Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment specific configuration #18

Open
guiocavalcanti opened this issue May 18, 2011 · 2 comments
Open

Environment specific configuration #18

guiocavalcanti opened this issue May 18, 2011 · 2 comments

Comments

@guiocavalcanti
Copy link

As in documentcloud/jammit@135103b, jammit now supports environment specifc configurations. I was wondering if I could use such feature in jammit-s3 (to define different buckets per environment).

@robcole
Copy link

robcole commented Jun 14, 2011

Would love to see this as well - having issues right now with staging vs. development vs. production environments.

@guiocavalcanti
Copy link
Author

@robcole, a possible workaround is run the jammit-s3 command passing the --config PATH option. My deployment recipe is aware which environment is being deployed , so I can specify which asset.yml file to use. For exaple jammit-s3 --config config/asset-production.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants