Hello,
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:
https://github.com/Scribery/meta/blob/master/playback_ui_cockpit_design.md
Kyrylo Gliebov
Software Engineer
Red Hat Czech
Cockpit Devs:
As we talked about earlier, we need to expose more Linux users to
Cockpit. As such, I wanted to let you know about a few upcoming
conferences which are heavily patronized by Linux admins and would be a
good place to start:
Usenix LISA https://www.usenix.org/conference/lisa17
Deadline Monday, April 24, 2017, 11:59 pm PDT
Open Source Summit (was LinuxCon)
http://events.linuxfoundation.org/events/open-source-summit-north-america
Deadline May 6, 2017
Open Source Summit Prague
http://events.linuxfoundation.org/events/open-source-summit-europe
Deadline July 8, 2017
... there will be others as the calendar progresses (as well as
Meetups). If anyone is interested in presenting to external audiences
about Cockpit, please let me know ... I can help with reviewing
conference submissions, travel funding and more.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
=================
#cockpit: meeting
=================
Meeting started by mvollmer at 13:01:38 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2017-08-28/meeting.2017-08-28-13.…
.
Meeting summary
---------------
* 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
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mvollmer (26)
* dperpeet (6)
* zodbot (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi,
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
https://github.com/mvollmer/cockpit-apps-bin.git
into ~/.local/share/cockpit:
$ 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
with:
https://copr.fedorainfracloud.org/coprs/mvo/cockpit-app-freeipa/
# dnf copr enable mvo/cockpit-app-freeipa
# dnf install appstream-data-mvo
Two applications should spontanously appear in Cockpit, ready to be
installed.
What do you think? Does it work? Is it confusing?
Thanks!
Hi!
We're organizing a Cockpit workshop in the two days preceding All
Systems Go! conference [1] 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
general architecture.
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!
Cheers
Lars
[1] All Systems Go! is the more broad successor to last year's
systemd.conf:
https://all-systems-go.io/
ignatenkobrain asked on #cockpit to describe our requirements around
javascript debuginfo so those can be taken into account in efforts such as:
https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo
Here they are:
* Cockpit is written mostly in javascript.
* This javascript runs in the browser. The browser may not be
a Linux system. This means Cockpit code as installed in Fedora
Debian or Ubuntu is actually running on a Mac, Windows, or Linux.
* Browsers load .map files that live next to the javascript .js
files which are loaded. They make an HTTP request for this data.
* Cockpit assets loadable by the browser are placed in
/usr/share/cockpit/<package>/ directories
This is documented here:
http://cockpit-project.org/guide/latest/packages.html
* The map files should be available for loading into the web browser
when cockpit-debuginfo is installed in order to provide assistance in
debugging Cockpit.
* The map files are not architecture specific, but are tightly bound
to the Cockpit javascript that is installed.
* The map files are produced by a myriad of technologies. In Cockpit's
case these are 'webpack', 'uglify-js' and 'less'. These technologies
change rapidly over time, as does much about javascript :S
* There are also map files for stylesheets and other loadable
assets on the page. These non-javascript debuginfo should be
handled in the same way.
More info:
https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
File format:
https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
Hope that helps,
Stef