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

DigitalOcean migration – Critical Path #57

Closed
5 of 11 tasks
Tracked by #59
guylepage3 opened this issue Oct 14, 2019 · 3 comments
Closed
5 of 11 tasks
Tracked by #59

DigitalOcean migration – Critical Path #57

guylepage3 opened this issue Oct 14, 2019 · 3 comments
Assignees
Labels
critical path General list and critical item(s)
Projects

Comments

@guylepage3
Copy link
Contributor

guylepage3 commented Oct 14, 2019

Description
We should be running each service on it's own instance so that we can utilize them across various products. Having said that, we need to pull out all back-end services out of web app, setup, run and test each service on their own instance (Digital Ocean), run the client (front-end) on it's own instance, then connect the back-end services to the front-end through API calls.

Goals
Pull out back-end services from current web app, have the back-end, the front-end running on their own instances and have them talking to each other on Digital Ocean.

NOTE: Execute in chronological order

Tasks

NOTE
@faddat Once all items in this issue are complete, write up findings and then close #56 Understand how to run node.js apps on VM's issue. Thx.

Server split examples

References

  • Express - Web framework for Node.js.
  • Morgan - HTTP request logger middleware for node.js.
  • CORS - CORS is a node.js package for providing a Connect/Express middleware that can be used to enable CORS with various options.
  • Body Parser - Node.js body parsing middleware.
@guylepage3
Copy link
Contributor Author

@faddat this should be a great start. I am moving over to my other tasks for the evening. Let's chat about things once you've finished Task 1.

@guylepage3
Copy link
Contributor Author

guylepage3 commented Oct 15, 2019

@faddat I've pulled out our "Mailchimp subscription server" and set everything up for you to deploy the api to digital ocean. https://github.com/universelabs/universe-subscriptions.

Here's your issue for deploying the subscription Mailchimp server. #1 Deploy & setup subscription server server on Digital Ocean

@guylepage3
Copy link
Contributor Author

guylepage3 commented Oct 15, 2019

@faddat I've pulled out our "Nodemailer server" and set everything up for you to deploy the api to digital ocean. https://github.com/universelabs/universe-nodemailer.

Here's your issue for deploying the Nodemailer server. #1 Deploy & setup Nodemailer server server on Digital Ocean

@guylepage3 guylepage3 changed the title Digital Ocean migration – Critical Path DigitalOcean migration – Critical Path Oct 21, 2019
@guylepage3 guylepage3 transferred this issue from universelabs/universe.engineering Oct 21, 2019
@guylepage3 guylepage3 added the critical path General list and critical item(s) label Oct 21, 2019
@guylepage3 guylepage3 moved this from To do to Current focus in Universe 12 Oct 21, 2019
@guylepage3 guylepage3 removed this from Current focus in Universe 12 Nov 12, 2019
@guylepage3 guylepage3 added this to To do in Universe 13 via automation Nov 12, 2019
@guylepage3 guylepage3 moved this from To do to Current focus in Universe 13 Nov 12, 2019
@guylepage3 guylepage3 removed this from Current focus in Universe 13 Jan 7, 2020
@guylepage3 guylepage3 added this to To do in Universe 14 via automation Jan 7, 2020
@guylepage3 guylepage3 moved this from To do to Current focus in Universe 14 Jan 7, 2020
Universe 14 automation moved this from Current focus to Done Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical path General list and critical item(s)
Projects
Universe 14
  
Done
Development

No branches or pull requests

2 participants