WIP Use uWSGI to serve the app in production #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We can't use '.dev' or '.local' to name hosts for local development. '.dev' is a TLD and doesn't work under Vagrant (see Varying-Vagrant-Vagrants/VVV#544). '.local' clashes with MDNS. According to RFC 6761 '.test' is reserved for local networks, so let's use that.
The old invoke file was based on our invoke file from our conduit hg monorepo - which had many different containers building and running in unision. In our case we're using invoke simply as an alias for docker-compose to prevent us from having to type everything out. The old invoke file created a new project space for the test containers which was causing problems because changes to the Dockerfile or the python requirements wouldn't cause rebuild of images in the testproject space (unknown reason why). So what would happen is I would run `invoke test` but I would get a build failure even though everything looked fine on my end - the underlying cause was that the test container wasn't refreshed and it was not obvious when this happened. This commit changes the tasks.py file to use the same project space as the normal development one. Now if the tests are failing it is because of a problem that you should also have encountered when running the dev containers.
With the addition of the Auth0 changes, the Flask app now requires that the SERVER_NAME config be set and be exactly the equal to the host:port that the site is accessed by. In the test environment that host:port is lando-ui:7777. This commit updates the tests to set that and also updates the click configuration to not set a default SESSION_COOKIE_DOMAIN since that should always be set by whoever is creating the app.
Build and configure the uWSGI application server for use in production environments. The default configuration is to serve connections over the uwsgi protocol to an nginx web head.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on mozilla-conduit/lando-api#14. See that PR for details.