I'm working on Session Recording UI for Cockpit.
It might become a separate module or part of Cockpit master.
We together with Nikolai Kondrashov want to start the discussion
about design to match your standard of Cockpit project.
Here some design ideas for Session Recording:
Red Hat Czech
Meeting started by mvollmer at 13:01:38 UTC. The full logs are available
* Agenda (mvollmer, 13:01:43)
* Applications (mvollmer, 13:04:31)
* any other business (mvollmer, 13:15:10)
Meeting ended at 13:20:23 UTC.
Action Items, by person
People Present (lines said)
* mvollmer (26)
* dperpeet (6)
* zodbot (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
I am working on "Applications" Cockpit: a way to install additional
software on your server, such as FreeIPA.
If you are on Fedora 26, you can try this out, and I am very much
interested in feedback of any kind.
To get started, clone this repository
$ mkdir -p ~/.local/share/cockpit
$ cd ~/.local/share/cockpit
$ git clone https://github.com/mvollmer/cockpit-apps-bin.git
Then re-login to Cockpit. You should now see a new "Applications"
entry in the shell navigation menu.
You can use a COPR with some demo packages to get something to play
# dnf copr enable mvo/cockpit-app-freeipa
# dnf install appstream-data-mvo
Two applications should spontanously appear in Cockpit, ready to be
What do you think? Does it work? Is it confusing?
We're organizing a Cockpit workshop in the two days preceding All
Systems Go! conference  in Berlin — on the 19th and 20th of October.
The idea is to bring the Cockpit community together to help each other
out in various areas relating to Cockpit. For example, getting started
writing a module, tackling beginner tasks, or understanding Cockpit's
If you're interested, please let us know (either on this list or to me
directly) that you're planning on coming and which topics you'd like to
learn or teach about. This will help us to plan accordingly.
Also, spread the word if you like the idea!
 All Systems Go! is the more broad successor to last year's
ignatenkobrain asked on #cockpit to describe our requirements around
Here they are:
a Linux system. This means Cockpit code as installed in Fedora
Debian or Ubuntu is actually running on a Mac, Windows, or Linux.
files which are loaded. They make an HTTP request for this data.
* Cockpit assets loadable by the browser are placed in
This is documented here:
* The map files should be available for loading into the web browser
when cockpit-debuginfo is installed in order to provide assistance in
* The map files are not architecture specific, but are tightly bound
* The map files are produced by a myriad of technologies. In Cockpit's
case these are 'webpack', 'uglify-js' and 'less'. These technologies
* There are also map files for stylesheets and other loadable
handled in the same way.
Hope that helps,