Burak Ozter
1f9dea648f
|
||
|---|---|---|
| .. | ||
| .cockpit-ci | ||
| .fmf | ||
| .github | ||
| packaging/debian | ||
| plans | ||
| po | ||
| src | ||
| test | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .gitmodules | ||
| .stylelintrc.json | ||
| HACKING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| build.js | ||
| me.chabad360.docker.metainfo.xml | ||
| node-modules-fix.sh | ||
| package.json | ||
| packit.yaml | ||
| pyproject.toml | ||
README.md
cockpit-docker
This is the Cockpit user interface for docker containers.
Technologies
-
cockpit-docker communicates to docker through its REST API.
-
This project is based on cockpit-podman, I ported as much as I could to the docker API, but not everything maps (e.g. pods) and not everything is ported yet.
Development dependencies
On Debian/Ubuntu:
$ sudo apt install gettext nodejs make
On Fedora:
$ sudo dnf install gettext nodejs make
Getting and building the source
These commands check out the source and build it into the dist/ directory:
git clone https://github.com/cockpit-docker/cockpit-docker
cd cockpit-docker
make
Installing
sudo make install installs the package in /usr/local/share/cockpit/. This depends
on the dist target, which generates the distribution tarball.
You can also run make rpm to build RPMs for local installation.
In production mode, source files are automatically minified and compressed.
Set NODE_ENV=production if you want to duplicate this behavior.
Arch Derivatives
yay -Ss cockpit-docker
OR for Manjaro
pamac install cockpit-docker
Development instructions
See HACKING.md for details about how to efficiently change the code, run, and test it.
Automated release
The intention is that the only manual step for releasing a project is to create a signed tag for the version number, which includes a summary of the noteworthy changes:
123
- this new feature
- fix bug #123
Pushing the release tag triggers the release.yml GitHub action workflow. This creates the official release tarball and publishes as upstream release to GitHub.
The Fedora and COPR releases are done with Packit, see the packit.yaml control file.
Automated maintenance
It is important to keep your NPM modules up to date, to keep up with security updates and bug fixes. This happens with dependabot, see configuration file.
Translations are refreshed every Tuesday evening (or manually) through the weblate-sync-po.yml action. Conversely, the PO template is uploaded to weblate every day through the weblate-sync-pot.yml action.