This is a summary of the Cockpit weekly release ... yup we missed a couple weeks. This week it was 0.96
Cockpit now limits authentication requests ------------------------------------------
Cockpit now keeps itself from spawning too many processes to handle authentication requests. The cockpit-ws process has a MaxStartups option similar to sshd. It lets you set the maximum number of authentications that can be in progress, as well as a drop rate for times when that limit is exceeded.
The default has been set to 10 simultaneous authentication requests.
Doc: http://cockpit-project.org/guide/latest/cockpit.conf.5.html Change: https://github.com/cockpit-project/cockpit/pull/3830
Compatible with docker 1.0 --------------------------
Docker 1.10 has or will change its APIs in several ways, mostly getting stricter on validating its input and deprecating old stuff. This version of Cockpit has several updates to make things continue to work.
Change: https://github.com/cockpit-project/cockpit/pull/3823
Showing disk names and icons ----------------------------
Andreas has been working on getting the storage display to look and react better. And mulkieran has been doing lots of testing in this area so more to come.
Change: https://github.com/cockpit-project/cockpit/pull/3792 Change: https://github.com/cockpit-project/cockpit/pull/3714 Change: https://github.com/cockpit-project/cockpit/pull/3738
Fixed several memory leaks --------------------------
Although we run the unit tests with valgrind, the valgrind process was being killed when the javascript based tests were done. So we missed fixing a few memory leaks, mostly to do with DBus messages. These are fixed now.
Change: https://github.com/cockpit-project/cockpit/pull/3845
Better Vagrant support ----------------------
Lars made the Vagrantfile better by adding support for logging into Cockpit with the 'vagrant' user, and removing the TLS requirement when you're developing via Vagrant.
So just do this to start hacking on Cockpit:
$ git clone http://github.com/cockpit-project/cockpit $ cd cockpit $ sudo vagrant up $ firefox http://localhost:9090
See HACKING.md for more info:
https://github.com/cockpit-project/cockpit/blob/master/HACKING.md
Integration tests can be run against an already running machine ---------------------------------------------------------------
Besides finding bugs in Cockpit, the Cockpit integration tests have been finding all sorts of bugs in other software that Cockpit drives. So it's cool to see others starting to try to run these same tests as part of their testing process.
One thing that makes it easier is that you can pass a --machine argument to many of the 'verify' tests and instead of trying to spawn a new machine, it'll run the test against an already running machine that you may have set up.
Something like this:
$ cd test $ ./verify/check-system-info --machine=10.1.1.2
Get it ------
You can get Cockpit 0.96 in Fedora 23 or Fedora Rawhide:
https://bodhi.fedoraproject.org/updates/cockpit-0.96-1.fc23
Or via COPR for CentOS, RHEL, and earlier versions of Fedora:
https://copr.fedoraproject.org/coprs/g/cockpit/cockpit-preview/
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/0.96
Take care,
Stef