-
Notifications
You must be signed in to change notification settings - Fork 1
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
Refactor & move client (universe.engineering) to DigitalOcean #71
Labels
refactoring
Refactoring related item(s) and issue(s)
Projects
Comments
guylepage3
changed the title
Move app from Heroku to Netlify or GCP
Move app from Heroku to GCP
Sep 23, 2019
guylepage3
changed the title
Move app from Heroku to GCP
Move website (web app) from Heroku to GCP
Sep 23, 2019
@faddat let me know if you need anything here. I am happy to walk you through Heroku. |
Great work on this so far @faddat. |
@faddat I just added Full Node.js Deployment - NGINX, SSL With Lets Encrypt to the references list. I'll go through this tutorial in the morning and apply it to the app. |
guylepage3
changed the title
Move website (web app) from Heroku to GCP
Move website (web app) from Heroku to DigitalOcean
Oct 1, 2019
Taking over this issue. |
guylepage3
changed the title
Move website (web app) from Heroku to DigitalOcean
Move web client from Heroku to DigitalOcean
Oct 15, 2019
guylepage3
changed the title
Move web client from Heroku to DigitalOcean
Move web client from Heroku to Digital Ocean
Oct 15, 2019
guylepage3
added
refactoring
Refactoring related item(s) and issue(s)
and removed
enhancement
Product and project enhancement item(s)
labels
Oct 21, 2019
guylepage3
changed the title
Move web client from Heroku to Digital Ocean
Refactor web client for transfer to DigitalOcean
Oct 21, 2019
guylepage3
changed the title
Refactor web client for transfer to DigitalOcean
Refactor wRefactor and move web client from Heroku to Digital Ocean
Oct 21, 2019
guylepage3
changed the title
Refactor wRefactor and move web client from Heroku to Digital Ocean
Refactor and move web client from Heroku to Digital Ocean
Oct 21, 2019
guylepage3
changed the title
Refactor and move web client from Heroku to Digital Ocean
Refactor and move web client from Heroku to DigitalOcean
Oct 21, 2019
27 tasks
guylepage3
changed the title
Refactor and move web client from Heroku to DigitalOcean
Refactor & move client (universe.engineering) to DigitalOcean
Oct 21, 2019
This was referenced Oct 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Refactor & move client (universe.engineering) from Heroku to DigitalOcean.
Heroku requires a static IP in order to configure a root domain. We, at Universe, must configure our DNS to root as we cannot have our apps resolving to
www.universe.engineering
. Our DNS must resolve touniverse.engineering
as our TLD is so long and confusing for folks. we’ve received a lot of feedback on this issue.The catch is that Heroku requires a static IP configuration and Heroku is the only hosting provider out there that does not work with
A records
for root domains.Heroku’s solution is to use dnsimple.com for aliasing. they have worked with them to provide this service.
So technically, we need to get off DNSimple.com but since we need to resolve to a root domain, we now need to move off of Heroku.
Tasks
NetlifyorGCPor ✅DigitalOcean.#56 Understand how to run node.js apps on VM'sReferences
The text was updated successfully, but these errors were encountered: