d1b7154026
Currently, crash reporting is done by running the command-line tool, which asks for user input on the standard streams. This completely breaks most workflows, as, for example, one needs to log in to their RH Bugzilla account to file a bug, but the prompt is shown on the server-side only. reportd was written for the express purpose of dealing with such cases. With version 0.5, it supports signaling clients about incoming prompts and provides an API to deal with them. Closes: #11150 |
||
---|---|---|
.cockpit-ci | ||
.github/ISSUE_TEMPLATE | ||
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