Feature: Deploy & SSL #18
Merged
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.
There's a new branch
deploy.deploybranch is used in CI/CD workflows to automatically deploy/redeploy changes to DigitalOcean droplets.deploy.netcreate-itestandnetcreate-deploy-dorepos to manage deployments.deploybranch is protected and cannot be deleted.netcreate-deploy-doin thev0.4branch caf40d4New Features
nc-multiplexportnc-multiplexexpress server runs on port 80, redirecting traffic to other running graphs on ports 3000+ and 4000+. In order to support HTTPS, we need to add an NGINX reverse proxy that initially runs on port 80 to validate the LetsEncrypt certbot, then afterwards support redirecting port 443 to thenc-multiplexexpress server. This means the express server needs to run on a different port.--port=xxxxto define a custom port to use when startingnc-multplex, e.g../nc-multiplex.js --port=8080.DEFAULT_PORTport 80 is used.start-nc-multiplex-ssl.shthat starts multiplex on port 8080. This is referenced by theNCPLEX_PORTvariable in thenetcreate-deploy-docreate_droplet_ansible_docker.ymlaction. SeeNCPLEX_PORT:53nginx-ssl.conf.j2file that routes port 443 traffic to the app running on the express server.client-network.jsnow supports secure web sockets. Ifhttpsis detected in the URL, then websocket traffic is now directed towss://<url>/ws_port/<port>instead ofws://<url>:<port>.netcreate-itestin thedeploybranch #404