Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upconfig:push with .env doesn't handle export or double quotes #289
Comments
|
From @mboersma on June 10, 2015 21:24 Are env vars containing spaces in their names legal on Heroku? If not, we should tighten the .env file validation rules; if so, we should probably document |
|
From @bacongobbler on June 18, 2016 7:14 same answer as I laid out in deis/deis#4512; we should move to a shared library or follow the spec laid out in https://github.com/bkeepers/dotenv#usage. |
|
We're had the same bug a few times. Locally they work fine using Foreman, but in prod they fail. |
|
This issue was moved to teamhephy/workflow-cli#13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @glenwong on June 4, 2015 23:19
If you have environment variables in your .env file that are surrounded by double quotes or start with an export they aren't handled correctly when pushed to deis. For example:
export REDIS_URL="redis://localhost:6379"
ends up as
export REDIS_URL: "redis://localhost:6379"
Where "export REDIS_URL" is the key and the value is still surrounded by double quotes which can then cause things to fail when the config is referenced.
Copied from original issue: deis/deis#3796