Reverse proxy configurations for nginx, for development as well as production#25
Closed
jtnystrom wants to merge 68 commits intokosugi/angular-dockerfrom
Closed
Reverse proxy configurations for nginx, for development as well as production#25jtnystrom wants to merge 68 commits intokosugi/angular-dockerfrom
jtnystrom wants to merge 68 commits intokosugi/angular-dockerfrom
Conversation
…e, together with its routing.
fetching updates from master branch
Fetch networks from the server
…ization Merge master into visualization-working
…onent refactoring.
Add UI for importing/exporting gene sets from/to TargetMine
… Currently as permanent label display.
A couple minor fixes
Rodolfo/add viz component
Merge network visualization into master
…ts purpose better. Set the build destination for this to Toxygates/scalatra-jetty and update .gitignore accordingly.
…n the docker environment using a multi-stage build. Added a special ivy_cache.xml to help with pre-populating the ivy cache when the docker image gets built (slow step).
…(FUSIONAUTH_APP_URL)
…nce the latter contains musl instead of libc, and this confuses jne-kyotocabinet when it tries to find the right native library
Make angular/nginx/conf.d configurable in docker-compose, so that we can track different configurations for production and for development use. In conf.d/default (for development use), provide a reverse proxy for /json so that angular can talk to scalatra. In conf.d.prod/default, additionally provide a reverse proxy for fusionauth, so that fusionauth and node can live on the same port and server, separated only by the domain name in the request.
Docker image for scalatra + separate docker-compose.yml for production
…DME.md (build process)
Contributor
Author
|
(This branch was merged as part of #26) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Reverse proxies on the old server, which we are migrating from, were handled by apache, which was forwarding requests based on domain name and URL to tomcat. In the new docker-based setup, it is convenient to rely on nginx for this, since we are serving node from nginx anyway.
This PR makes angular/nginx/conf.d configurable in docker-compose, so that we can use different configurations for production and development.
Two alternatives are provided: conf.d (the old configuration, for development use) provides a reverse proxy for /json so that angular can talk to scalatra.
In conf.d.prod, additionally we provide a reverse proxy for fusionauth, so that fusionauth and node can live on the same port and server, separated only by the domain name in the request.
The configuration directory is set in docker-compose.yml for the node service as follows: