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
Allow for rapid changes to DOMAIN_NAME (which currently appears to be hard-coded in a number of files.)
Rationale
It should be possible / straightforward to test the production deployment on a staging machine that is behind the company firewall by simply using a configuration variable (e.g. a value set in the .env file) with that machine's name or IP Address.
Production deployment as written requires SSL via letsencrypt, right? So changing resolve.conf alone isn’t an option if the machine can’t obtain certs...
Description
Allow for rapid changes to DOMAIN_NAME (which currently appears to be hard-coded in a number of files.)
Rationale
It should be possible / straightforward to test the production deployment on a staging machine that is behind the company firewall by simply using a configuration variable (e.g. a value set in the .env file) with that machine's name or IP Address.
Use case(s) / visualization(s)
None.
References
See also #1082
The text was updated successfully, but these errors were encountered: