mirror of
https://github.com/cockpit-project/cockpit.git
synced 2026-11-03 21:49:50 -09:00
ad4176e4ca
Making test-functions strict required some test adjustments where we incorrectly expected an number while we receive in fact a string. As getAttribute() returns either a string or null. |
||
|---|---|---|
| .. | ||
| flatpak | ||
| ws | ||
| Makefile.am | ||
| README.md | ||
Cockpit Containers
- ws: Cockpit's web server, for installation on CoreOS; uses SSH to connect to the local host or remote machines
- bastion: A reduced variant of the web server that runs unprivileged, and can only connect to remote machines. Suitable for deploying on e.g. Kubernetes. This is currently a prototype.
- unit-tests: Our project's unit tests run in this container; usually on GitHub PRs, but you can also run it locally for reproducing failures.
- flatpak: Scripts for locally building, running, and testing our Cockpit Client flatpak.
See the individual README.md files in the subdirectories for details.
ws container development
Build the container:
make ws-container
You can install locally built RPMs by copying them into the ws/rpms/
directory.
For fast iteration, you can also build the container with the binaries
(cockpit-ws, cockpit-tls, etc.) and the pages (dist/*) from the local
build tree. For that to work, you have to build the project on the same OS as
the container, and configure with --prefix=/usr. No warranties, you have to
know what you are doing!
make ws-container-build-tree
Run the built container and log in interactively as a shell:
make ws-container-shell
When running docker the 'sudo' command will be used to get necessary privileges.