3b5026bdf1
The vast majority don't apply any more to current library versions in our unit-tests container. glib.supp had lots of patterns that are shipped by glib2-devel/libglib2.0-dev in /usr/share/glib-2.0/valgrind/glib.supp, so remove these and use the system-provided one instead. Unfortunately there does not seem to be a pkgconfig variable for it, but the path is the same on Fedora, RHEL, CentOS and Debian. Closes #12760 |
||
---|---|---|
.cockpit-ci | ||
.github/ISSUE_TEMPLATE | ||
bots | ||
containers | ||
doc | ||
eslint-plugin-cockpit | ||
examples | ||
node_modules | ||
pkg | ||
po | ||
src | ||
test | ||
tools | ||
.eslintignore | ||
.eslintrc.json | ||
.flowconfig | ||
.gitignore | ||
.tasks | ||
.travis.yml | ||
AUTHORS | ||
COPYING | ||
HACKING.md | ||
Makefile.am | ||
README.md | ||
Vagrantfile | ||
autogen.sh | ||
configure.ac | ||
package.json | ||
webpack.config.js |
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.
On the Cockpit dashboard, you can easily add other machines with Cockpit installed that are accessible via SSH.
Development
- Making changes to Cockpit
- How to contribute, developer documentation
- IRC Channel: #cockpit on FreeNode
- Mailing List
- Guiding Principles
- Release Notes
- Privacy Policy