Managing outdated pull requests is time-consuming. Mergify's Merge Queue automates your pull request management & merging. It's fully integrated to GitHub & coordinated with any CI. Start focusing on code. Try Mergify for free. Learn more →
Config Alternatives
Similar projects and alternatives to config
-
-
-
Mergify
Tired of breaking your main and manually rebasing outdated pull requests?. Managing outdated pull requests is time-consuming. Mergify's Merge Queue automates your pull request management & merging. It's fully integrated to GitHub & coordinated with any CI. Start focusing on code. Try Mergify for free.
-
-
-
cue
The home of the CUE language! Validate and define text-based and dynamic configuration
-
dotenv
A twelve-factor configuration (12factor.net/config) library for Java 8+ (by shyiko)
-
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
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
-
-
gestalt
A Java configuration library that allows you to build your configurations from multiple sources, merges them and convert them into an easy-to-use typesafe configuration class. A simple but powerful interface allows you to navigate to a path within your configurations and retrieve a configuration object, list, or a primitive value. (by gestalt-config)
-
-
-
-
-
-
-
tab-rs
The intuitive, config-driven terminal multiplexer designed for software & systems engineers
-
Sonar
Write Clean Java Code. Always.. Sonar helps you commit clean code every time. With over 600 unique rules to find Java bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
config reviews and mentions
-
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.
This is one of the few HN discussions where I feel a little bit qualified to give an opinion :)
Two years ago I started a small data quality checker software where users could define their alerts, frequencies,.. all in config files instead of modifying code.
I started with JSON as config format, but then realised comments are necessary to guide users in defining alerts. I moved to YAML, but after some "indentation incodents" started using HOCON conf [0] and never looked back. I don't see any reason for choosing YAML over one of JSON or HOCON, except being forced to. Features such as inheritance and text block support which were essential for me are nicely supported in HOCON.
- 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
For reading configuration files, I would probably use this: https://github.com/lightbend/config instead of Spring.
"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.
-
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
-
A note from our sponsor - Mergify
blog.mergify.com | 23 Sep 2023
Stats
lightbend/config is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of config is Java.