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
As some cool kid using soggy, I'd like to be able to deploy an application across multiple environments using the same code base, switching configuration used on an environment variable (GO_ENV maybe).
Maybe a JSON file per environment and a way to initialise the server dependant on it's GO_ENV?
The text was updated successfully, but these errors were encountered:
@dbrain I just discovered your project recently. Looks great.
I'd recommend GOLANG_ENV, or even the more specific SOGGY_ENV to avoid name collisions. But I recommend keeping it simple at first, so as to avoid complexity that never gets used. :)
@asenchi Thanks!
Good call. If I go ahead with this issue I'll probably go with SOGGY_ENV. This is fairly low on the priority list at the moment, so I'll reassess the need for it when I get to it. Mostly just a brain dump because I have a horrible memory ;)
As some cool kid using soggy, I'd like to be able to deploy an application across multiple environments using the same code base, switching configuration used on an environment variable (GO_ENV maybe).
Maybe a JSON file per environment and a way to initialise the server dependant on it's GO_ENV?
The text was updated successfully, but these errors were encountered: