You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon redeploying an app (having previously created a db and linking the existing app to the db) the redeployed app does not have access to the previously set DATABASE_URL. This makes sense because the new container won't have the env vars so my question is what is the preferred way to programmatically set the DATABASE_URL env var for a frequently deployed app? #23 seems promising but I still can't quite figure out what's going on. Also, this issue from docker seems promising but doesn't appear to automatically set env vars: moby/moby#240
The text was updated successfully, but these errors were encountered:
Upon redeploying an app (having previously created a db and linking the existing app to the db) the redeployed app does not have access to the previously set DATABASE_URL. This makes sense because the new container won't have the env vars so my question is what is the preferred way to programmatically set the DATABASE_URL env var for a frequently deployed app?
#23 seems promising but I still can't quite figure out what's going on. Also, this issue from docker seems promising but doesn't appear to automatically set env vars: moby/moby#240
The text was updated successfully, but these errors were encountered: