From 00b1277fad40aaf6a25fa73b83c08b81deb97da1 Mon Sep 17 00:00:00 2001 From: Karl Matthias Date: Fri, 17 Apr 2015 08:42:02 -0700 Subject: [PATCH] Add to README. --- README.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/README.md b/README.md index 06d43cca..e0d4f911 100644 --- a/README.md +++ b/README.md @@ -426,6 +426,11 @@ end Development ----------- +Centurion supports a few features to make development easier when +building your deployment tooling or debugging your containers. + +#### Overriding Environment Variables + Sometimes when you're doing development you want to try out some configuration settings in environment variables that aren't in the config yet. Or perhaps you want to override existing settings to test with. You can provide the @@ -441,6 +446,24 @@ this functionality for production deployments. It will work, but it means that the config is not the whole source of truth for your container configuration. Caveat emptor. +#### Exporting Environment Variables Locally + +Sometimes you need to test how your code works inside the container and you +need to have all of your configuration exported. Centurion includes an action +that will let you do that. It exports all of your environment settings for the +environment you specify. It then partially sanitizes them to preserve things +like `rbenv` settings. Then it executes `/bin/bash` locally. + +The action is named `dev:export_only` and you call it like this: + +```bash +$ bundle exec centurion -e development -p testing_project -a dev:export_only +$ bundle exec rake spec +``` + +It's important to note that the second line is actually being invoked with new +environment exported. + Future Additions ----------------