Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe how to use a local machine for testing a production deployment #1873

Open
gamesbook opened this issue Nov 20, 2018 · 2 comments
Open
Labels

Comments

@gamesbook
Copy link

gamesbook commented Nov 20, 2018

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

@japrogramer
Copy link

you could easily alter your resolve.conf to point to your local ip and port

@kevinseelbach
Copy link

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants