Since version 152, Cockpit can discover and install packages that addpages to Cockpit. We call them “Applications” and as of now, only twoof them exist: We have Fleet Commander and Cockpit’s own DiagnosticReports in Fedora. You might have seen them on the Applications page:If you want your own page to...
- Building and interacting with a test VM
- Using testvm.py in your test suite
- The bare minimum
- Requirements for real projects
- Bootstrapping your way from zero to “works!”
- Using different technologies
Not all of the system APIs use DBus. So sometimes we find ourselves in a situation where we have to use REST (which is often just treated as another word for HTTP) to talk to certain parts of the system. For example Docker has a REST API.For this tutorial you’ll...
- Getting Started
- Testing a Pull Request
- Making a change
- Bringing the Vagrant VM in sync
Much of Cockpit interacts with the server using DBus. We have a powerful yet simple API for doing that, and you should use DBus too when building your own Cockpit user interfaces. For this tutorial you’ll need at least Cockpit 0.41. A few tweaks landed in that release to solve...
It’s real easy to create these components. Tools are components that show up in the Tools menu in Cockpit:For example the Terminal that you see there is implemented as a tool. But lets make ourselves another one. For this tutorial you’ll need Cockpit 0.41. You can install it in Fedora...
- Control channels
- Making a DBus method call
- Spawning a process
- Doing it over a WebSocket
- And on it goes