conform alternatives and similar packages

Based on the "Configuration" category.
Alternatively, view conform alternatives based on common mentions on social networks and blogs.

Vapor

8.9 0.0 conform VS Vapor

Runtime configuration system for Elixir
confex

8.3 0.0 conform VS confex

Useful helper to read and use application configuration from environment variables.

InfluxDB - Power Real-Time Data Analytics at Scale

Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

Promo www.influxdata.com

dotenv

7.6 0.0 conform VS dotenv

A port of dotenv to Elixir
hush

6.5 2.9 conform VS hush

Hush is a runtime configuration loader for Elixir applications
Skogsrå

6.1 5.3 conform VS Skogsrå

Library to manage OS environment variables and application configuration options with ease
weave

6.0 4.0 conform VS weave

DISCONTINUED. JIT configuration loader that works with Kubernetes and Docker Swarm.
ex_conf

5.0 0.0 conform VS ex_conf

DISCONTINUED. Simple Elixir Configuration Management.
Flasked

4.7 0.0 conform VS Flasked

DISCONTINUED. Injecting ENV vars into application configuration at runtime (12factor app for Elixir)
configparser_ex

3.2 0.0 conform VS configparser_ex

A simple Elixir parser for the same kind of files that Python's configparser library handles
hush_aws_secrets_manager

3.0 2.4 conform VS hush_aws_secrets_manager

An AWS Secrets Manager Provider for Hush
mahaul

2.9 4.3 conform VS mahaul

Supercharge your environment variables in Elixir. Parse and validate with compile time access guarantees, defaults, fallbacks and app pre-boot validations.
hush_gcp_secret_manager

2.8 2.4 conform VS hush_gcp_secret_manager

A Google Secret Manager Provider for Hush
figaro

2.7 0.0 conform VS figaro

Figaro for Elixir
figaro_elixir

2.0 0.0 conform VS figaro_elixir

Environmental variables manager based on Figaro for Elixir projects
sweetconfig

1.7 0.0 conform VS sweetconfig

something to forget about configuration in releases
Enux

0.6 4.5 conform VS Enux

utility package for loading, validating and documenting your app's configuration variables from env, json, jsonc and toml files at runtime and injecting them into your environment
CFEnv

0.1 0.0 conform VS CFEnv

Environmental helpers for cloudfoundry, parsing and returning values off VCAP_SERVICES and VCAP_APPLICATON

Do you think we are missing an alternative of conform or a related project?

Add another 'Configuration' Package

Popular Comparisons

README

Conform

See the full documentation here.

The definition of conform is "Adapt or conform oneself to new or different conditions". As this library is used to adapt your application to its deployed environment, I think it's rather fitting. It's also a play on the word configuration, and the fact that Conform uses an init-style configuration, maintained in a .conf file.

Deprecation Notice

IMPORTANT: I am discontinuing maintenance of this project moving forward, in favor of a replacement based on TOML, found here. It is has a formal specification and supports much richer ways of expressing complex data (maps and lists), and supports several Elixir data types out of the box. The toml-elixir library also provides a simple transformation mechnanism for extending the basic set of datatypes with your own (including structs and records). Everything you could accomplish with Conform is doable with toml-elixir, and in a cleaner, easier to maintain format. In addition, it has full support for Distillery 2.0's config provider framework, allowing you to natively configure your Elixir releases with TOML config files

If anyone is interested in taking over maintainership of this library, please reach out to me here via issue, or by email, and I'll be glad to discuss the transition with you.

Features

It provides the following features:

An easy-to-use configuration file to end-users and/or system administrators.
Post-processing of simplified configuration options to more complex forms required by your application, without pushing that complexity on the user.
Richly-typed configuration options, such as IP addresses, URIs, etc., with the ability to define your own types.
Automatic validation of end-user configuration against a schema
Keep documentation of configuration options synced up automatically
Hidden configuration options: hide advanced options from end-users, but leave them available for power users or developers
Allow fetching information dynamically when the configuration is evaluated.
Can be used with releases

Rationale

Conform was designed for Elixir applications which are deployed via releases built with exrm or distillery. It was created in order to resolve some painful issues with the configuration mechanisms provided out of the box by both Erlang and Elixir.

Elixir offers a convenient configuration mechanism via config/config.exs, but it has downsides:

To change config settings, it requires you to recompile your app to regenerate the app.config/sys.config files used by the VM. Alternatively you can modify the sys.config file directly during deployment, using Erlang terms. Neither of these things are ops-friendly, or necessarily accessible to sysadmins who may not understand Elixir or Erlang semantics.
You can put comments in config/config.exs, but once transformed to app.config/sys.config, those comments are lost, leaving sysadmins lost when trying to understand what configuration values are allowed and what they do.
There is no config validation
You can't offer a nice interface for configuration to your apps users via something akin to conform's translations. They have to know how to work in Elixir terms, which is pleasant enough for a dev, but not so much for someone unfamiliar with programming.

Conform is intended to fix these problems in the following way:

It uses an init-style configuration, which should be very familiar to any sysadmin.
It is intended to be used during the release process, once your app has been deployed.
Conform works by taking the schema, the .conf file, and config.exs if it is being used, and combines them into the sys.config file used by the Erlang VM. However, unlike config.exs, you can bring the .conf into production with you, and use it for configuration instead of sys.config. This means that the docs provided in your schema file are available to the users configuring your application in production. The .conf is validated when it is parsed as well, so your users will get immediate feedback if they've provided invalid config settings.

I'm glad to hear from anyone using this on what problems they are having, if any, and any ideas you may have. Feel free to open issues on the tracker or come find me in #elixir-lang on freenode.