Skip to content

Home

Jump to bottom
Jeff Felchner edited this page Jan 12, 2018 · 15 revisions

Chamber is the auto-encrypting, extremely organizable, Heroku-loving, CLI-having, non-extra-repo-needing, non-Rails-specific-ing, CI-serving configuration management library.

We looked at all of the options out there and thought something was still missing, so we wrote Chamber. We made it with lots of ❤ and we hope you like it as much as we do.

Our Ten Commandments of Configuration Management

  1. Thou shalt be configurable, but use conventions so that configuration isn't necessary
  2. Thou shalt seamlessly work with Heroku or other deployment platforms, where custom settings may be stored in environment variables
  3. Thou shalt seamlessly work with Travis CI and other cloud CI platforms
  4. Thou shalt not force users to use arcane long_variables_to_keep_their_settings_organized
  5. Thou shalt not require users keep a separate repo or cloud share sync just to keep their secure settings updated
  6. Thou shalt not be bound to a single framework like Rails (it should be usable in other frameworks as well as in plain Ruby projects)
  7. Thou shalt have an easy-to-use CLI for scripting
  8. Thou shalt allow certain settings to be encrypted separately to allow levels of access.
  9. Thou shalt be well documented with full test coverage
  10. Thou shalt not have to worry about accidentally committing secure settings

Basic Usage

You can view our Basic Usage Guide here. Otherwise, feel free to browse the wiki using the table of contents to the right.

Credits

Chamber was written by Jeff Felchner and Mark McEahern

The Kompanee

Chamber is maintained and funded by The Kompanee, Ltd.

The names and logos for The Kompanee are trademarks of The Kompanee, Ltd.

License

Chamber is Copyright © 2014-2018 Jeff Felchner and Mark McEahern. It is free software, and may be redistributed under the terms specified in the LICENSE file.

Kompanee Logo Copyright ©2023

  1. Release News
  2. Gem Comparison
  3. 12-Factor App Rebuttal
  4. Environment Variable Problems
    1. Lack of Complex Values
    2. Organization
    3. Environment Sharing
    4. Team Member Syncing
    5. Environment Syncing
    6. Local Settings
    7. Tracking Changes
  5. Installation
    1. Initialization
    2. In a Ruby Project
    3. In a Rails Project
    4. In a Rails Engine
    5. In a Sinatra Project
    6. In a Padrino Project
    7. In a Hanami Project
  6. Basics
    1. File Layout
    2. Defining Settings
    3. Accessing Settings
    4. Namespace Basics
      1. Inline Namespaces
      2. Host-Based Settings
    5. Encryption Basics
      1. Encrypting Your Settings
      2. Accessing Encrypted Settings
    6. Environment Variables
  7. Defining Settings
    1. ERB Preprocessing
    2. Runtime Values
    3. Dynamic Templating
  8. Accessing Settings
    1. Dig
  9. Verifying Settings
  10. Namespaces
    1. File-Based Namespaces
    2. Mix and Match
    3. Custom Namespaces
  11. Environment Variables
    1. Coercions
  12. Integrations
    1. Git Commit Hooks
    2. Cloud Services
  13. Encryption
    1. Keypair Encryption
    2. What Keys Can Do
    3. Encrypting Nested Structures
    4. Namespaced Key Pairs
    5. Re-Securing
    6. Loading Keys from ENV
  14. Advanced Usage
    1. Manually Specifying Settings Files
    2. Outputting Your Settings
    3. Specifying Multiple Namespaces
    4. Handling Duplicates/Collisions
    5. Extending Chamber
  15. Command Line Reference
    1. init
    2. show
    3. files
    4. sign
    5. secure
    6. unsecure
    7. compare

Clone this wiki locally