staging and production environment variables #223
Comments
I feel that it would be easier to just have something like |
This would also be a big help for me too, I will have a separate config for staging/demo that I would prefer to not store in a separate file. Not at all a showstopper as everything else has worked beautifully. |
FYI, and in the meantime, I've had good success with this hack in
And then you do |
Hey! Thank you for that. In case I don't have a CloudFront distribution for the staging environment, would the following work?
That would essentially return null values for the distribution and wildcard invalidation on non-production builds. Is that valid? I've posted this question on StackOverflow as well. |
Hi,
How do I pass to s3_website on the command line whether it's staging or production environment so that it picks up the dotenv .env.staging or .env.production files respectively? I can't see anything in the documentation.
thanks
The text was updated successfully, but these errors were encountered: