Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cockpit-project/cockpit-podman
Cockpit UI for podman containers
https://github.com/cockpit-project/cockpit-podman
Last synced: 3 months ago
JSON representation
Cockpit UI for podman containers
- Host: GitHub
- URL: https://github.com/cockpit-project/cockpit-podman
- Owner: cockpit-project
- License: lgpl-2.1
- Created: 2018-07-03T06:49:48.000Z (over 6 years ago)
- Default Branch: main
- Last Pushed: 2024-04-13T08:35:18.000Z (7 months ago)
- Last Synced: 2024-04-14T00:54:48.966Z (7 months ago)
- Language: JavaScript
- Size: 3.74 MB
- Stars: 387
- Watchers: 19
- Forks: 80
- Open Issues: 60
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# cockpit-podman
This is the [Cockpit](https://cockpit-project.org/) user interface for [podman
containers](https://podman.io/).
## Technologies
- cockpit-podman communicates to podman through its [REST API](https://podman.readthedocs.io/en/latest/_static/api.html).
- This project is based on the [Cockpit Starter Kit](https://github.com/cockpit-project/starter-kit).
See [Starter Kit Intro](http://cockpit-project.org/blog/cockpit-starter-kit.html) for details.
# 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-project/cockpit-podman
cd cockpit-podman
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.
# Development instructions
See [HACKING.md](./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/workflows/release.yml)
[GitHub action](https://github.com/features/actions) workflow. This creates the
official release tarball and publishes as upstream release to GitHub.
The Fedora and COPR releases are done with [Packit](https://packit.dev/),
see the [packit.yaml](./packit.yaml) control file.
# Automated maintenance
It is important to keep your [NPM modules](./package.json) up to date, to keep
up with security updates and bug fixes. This happens with
[dependabot](https://github.com/dependabot),
see [configuration file](.github/dependabot.yml).
Translations are refreshed every Tuesday evening (or manually) through the
[weblate-sync-po.yml](.github/workflows/weblate-sync-po.yml) action.
Conversely, the PO template is uploaded to weblate every day through the
[weblate-sync-pot.yml](.github/workflows/weblate-sync-pot.yml) action.