podman
config
podman | config | |
---|---|---|
2 | 32 | |
46 | 6,099 | |
- | 0.3% | |
8.3 | 3.0 | |
10 days ago | 15 days ago | |
HTML | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
podman
-
Make systemd better for Podman with Quadlet
You are correct. And there is an Ansible role for automated management: https://github.com/linux-system-roles/podman/
-
docker Vs podman - Which one is worth doing a dive in?
My opinion, yes, and RHEL are sure aiming for that. Whether they will succeed and whether it's better than Docker/ Kubernetes is down to personal opinion at least for now. Podman is trying to make it easy to work with it and to scale - there's an Ansible role under development. At the end of the day, Podman is made to be compatible with both Docker and Kubernetes syntax and general way of work, so I think if you know it well it shouldn't be too hard to learn the other technologies if needed.
config
- Hocon (Human-Optimized Config Object Notation)
-
XML is better than YAML
I don‘t understand why HOCON (https://github.com/lightbend/config/blob/main/HOCON.md) isn‘t used more often (at least for configuration use cases). It‘s a superset of JSON, has comments, multiline strings, optional quotes, replacement syntax. We use it at many places, and it‘s as nice at it can get.
- Toml-bench – Which toml package to use in Python?
- slf4j or System.Logger?
- TOML: Tom's Obvious Minimal Language
-
Ron: Rusty Object Notation
HOCON is a great human-readable alternative to JSON. It's a superset of JSON with lots of cool features that make it both more readable and easier to use.
Here's a rundown of HOCON's main features: https://github.com/lightbend/config#features-of-hocon
-
Spring and scala
"Typesafe Config" is the library generally used to read configuration files in HOCON format, which this library introduced. It's commonly used in essentially OOP/imperative Scala contexts, including Akka and its ecosystem.
-
Make systemd better for Podman with Quadlet
Interesting!
For my own servers I use an internal tool that integrates apps with systemd. You point it at the output of your build system and a config file, and it produces a deb that contains systemd unit files and which registers/starts the server on install/reboot/upgrade, as a regular debian package would. Then it uploads it to the server via sftp and installs it using apt, so dependencies are resolved. As part of the build process it can download and bundle language runtimes (I use it with a JVM), it scans native binaries to find packages that the app should depend on, and you can define your config including package metadata like dependencies and systemd units using the HOCON language [1].
Upshot is you can go from a Gradle or Maven build to a running server with a few lines of config. Oh and it can build debs from any OS, so you can push from macOS and Windows too. If your server needs to depend on e.g. Postgres, you just add that dependency in your config and it'll be up and running after the push.
It also has features to turn on DynamicUser and other sandboxing features. I think I'll experiment with socket activation next, and then bundled BorgBackup.
Net/net it's pretty nice. I haven't tried with containers because many language ecosystems don't seem to really need them for many use cases. If your build tool knows how to download your language runtime and bundle it sans container by just setting up paths correctly, then going without means you can rely on your Linux distribution to keep things up to date with security patches in the background, it means networking works as you'd expect (no accidentally opened firewall ports!) and so on. SystemD knows how to configure resource isolation/cgroups and kernel sandboxing, so if you need those you can just write that into your build config and it's done. Or not, as you wish.
With a deployment tool to automate builds/pushes, systemd to supervise processes and a big beefy dedicated machine to let you scale up, I wonder how much value the container part is really still providing if you don't need the full functionality of Kubernetes.
[1] https://github.com/lightbend/config/blob/main/HOCON.md
-
Introducing JXC: An extensible, expressive data language. It's a drop-in replacement for JSON and supports type annotations, numeric suffixes, base64 strings, and more!
Other similar standards: TOML, HOCON
-
Jsonnet is better than YAML for generating JSON
I've also used HOCON pretty extensively for config, and it is better than both YAML and JSON for config with moderate to high complexity.
What are some alternatives?
docker-nginx - Official NGINX Dockerfiles
cfg4j - Modern configuration library for distributed apps written in Java.
podman-nginx-socket-activation - Demo of how to run socket-activated nginx with Podman
owner - Get rid of the boilerplate code in properties based configuration.
patchew - A patch email tracking and testing system
dotenv - Loads environment variables from .env for nodejs projects.
podman - Podman: A tool for managing OCI containers and pods.
dotenv - A twelve-factor configuration (12factor.net/config) library for Java 8+
ansible-podman-collections - Repository for Ansible content that can include playbooks, roles, modules, and plugins for use with the Podman tool
Configur8 - Nano-library which provides the ability to define typesafe (!) configuration templates for applications.
centraldogma - Highly-available version-controlled service configuration repository based on Git, ZooKeeper and HTTP/2
json5 - JSON5 — JSON for Humans