0a51a881c3
starter-kit and derivatives don't understand the build.js `-r` option, only the environment variable. So properly handle the latter, and update the documentation to use the env variable, to get a common workflow for all our projects. Also fix the destination path, the rsync plugin moved to /usr/local/share/cockpit some time ago. |
||
---|---|---|
.cockpit-ci | ||
.fmf | ||
.github | ||
containers | ||
doc | ||
examples | ||
modules | ||
node_modules@055682f225 | ||
pkg | ||
plans | ||
po | ||
selinux | ||
src | ||
test | ||
tools | ||
.eslintignore | ||
.eslintrc.json | ||
.flake8 | ||
.flowconfig | ||
.gitignore | ||
.gitleaks.toml | ||
.gitmodules | ||
.stylelintrc.json | ||
AUTHORS | ||
COPYING | ||
HACKING.md | ||
Makefile.am | ||
README.md | ||
autogen.sh | ||
build.js | ||
configure.ac | ||
files.js | ||
package.json | ||
packit.yaml | ||
pyproject.toml |
README.md
Cockpit
A sysadmin login session in a web browser
Cockpit is an interactive server admin interface. It is easy to use and very lightweight. Cockpit interacts directly with the operating system from a real Linux session in a browser.
Using Cockpit
You can install Cockpit on many Linux operating systems including Debian, Fedora and RHEL.
Cockpit makes Linux discoverable, allowing sysadmins to easily perform tasks such as starting containers, storage administration, network configuration, inspecting logs and so on.
Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface.
You can also easily add other machines that have Cockpit installed and are accessible via SSH and jump between these hosts.