conferer: Configuration management library

[ configuration, library, mpl ] [ Propose Tags ]

Library to abstract the parsing of many haskell config values from different config sources

[Skip to Readme]


Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS],,,,,,,,,,,,
Change log
Dependencies base (>=4.3 && <5), bytestring (>=0.10 && <0.13), containers (>=0.5 && <0.7), directory (>=1.2 && <2.0), filepath (>=1.0 && <2.0), text (>=1.1 && <2.2) [details]
License MPL-2.0
Copyright (c) 2020 Lucas David Traverso
Author Lucas David Traverso
Revised Revision 5 made by ludat at 2024-01-08T08:56:46Z
Category Configuration
Home page
Bug tracker
Uploaded by ludat at 2021-03-01T05:06:22Z
Distributions LTSHaskell:, NixOS:, Stackage:
Reverse Dependencies 13 direct, 0 indirect [details]
Downloads 4709 total (48 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2021-03-01 [all 1 reports]

Readme for conferer-

[back to package description]


The problem

Have you ever tried configuring a Haskell application? If you are not the author you are usually out of luck and the only way to configure it is recompiling, and even if you are the author you have to write that logic yourself (reading env vars, files or cli params), what about partial updates? and environments? or error handling?

One solution: Conferer

Conferer is a library that defines ways of getting configuration for your Haskell application and the libraries it uses in a very ergonomical way.

Example: one Settings

Let's say I want to configure a warp server, then we'd do:

main = do
  -- First we create a Config, which defines which sources our config will be
  -- reading, by default cli params, env vars and .properties files
  config <- defaultConfig "awesomeapp"
  -- Then we use getFromConfig with some arbitrary key (to scope the server
  -- config) and we use our Config to generate a Warp Settings
  warpConfig :: Warp.Settings <- getFromConfig "server" config

  -- Afterwards we use the Settings as usual
  Warp.runSettings warpConfig myApp

Now I need to chage the port of the app, I can change it by either:

  • Setting cli params like ./myApp --server.port=5555
  • Setting an environment variable called AWESOMEAPP_SERVER_PORT=5555
  • In a config/ file, you can have server.port=5555

And you may also get that value from different configuration sources like redis, json file, dhall file or whichever you may need.

Example 2: many different values with defaults

Let's say I want to configure a warp server and a redis db (using hedis), To do that we'd do:

-- First we create our configuration record which holds all the configurations
-- our app needs
data AppConfig = AppConfig
  { appConfigWarp :: Settings
  -- ^- From Warp
  , appConfigHedis :: ConnectionInfo
  -- ^- From Hedis
  , appConfigSecret :: Text
  -- ^- Some custom value we need
  } deriving (Generic)
  -- ^- We need to derive Generic to derive FromConfig

-- This typeclass defines how to create our type from a bunch of string based
-- key/values, (which our Config is), for records we can derive it using
-- Generics
instance FromConfig AppConfig

-- Now we need a default value for our app, all apps should be able to work
-- at least somewhat stupidly even if the user doens't supply configurations
-- at all
instance DefaultConfig AppConfig where
  configDef = AppConfig
    { appConfigWarp = setPort 2222 configDef
    -- ^- We want the default Warp config but the port should be 2222
    --    if the config doesn't mention it
    , appConfigHedis = configDef 
    -- ^- defaults for hedis are ok
    , appConfigSecret = "very secret... shhh"
    -- ^- we decide some random default, notice that Text has no default
    --    so using configDef here won't compile

main = do
  -- Like last time we create the config
  config <- defaultConfig "awesomeapp"
  -- Then we use getFromRootConfig without a key since Generics on AppConfig
  -- already scoped everything inside itself and we use our Config to
  -- generate an AppConfig
  warpConfig :: AppConfig <- getFromRootConfig config

  -- Afterwards we use the Settings as usual
  Warp.runSettings warpConfig myApp

Now to configure our app we can use the same sources as before (env vars, cli, files, etc) but using the following flags we can configure:

  • --warp.port=5555: set warp's server port to 5555
  • --secret=real_secrets: set our custom secret to "real_secrets"
  • --hedis=redis://username:password@host:42/2: set hedis' connection to that
  • set hedis' connection host to

Existing sources

Sources usually incur in many dependencies so they are split into different packages

  • Json (depends on aeson)
  • Dhall (depends on dhall)
  • Yaml (depends on yaml)

Existing FromConfig instances

Default instances for fetching a values from a config (usually a config value for some library)


There are as well some utilities to change sources:

  • Conferer.Source.Namespace: All keys must be namespaced and the namespace is striped for lookup
  • Conferer.Source.Mapped: Using a map key to maybe key you can change the name of a key or even hiding some key
  • Conferer.Source.Simple: Get keys from a hardcoded map key to string

Future maybe things

  • Interpolate keys with other keys: {a: "db", b: "${a}_thing"}, getting b will give "db_thing" (maybe) even in different levels of configuration
  • A LOT of sources
  • A LOT of FromConfig implementations