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
Pull out Mailchimp Express server for DigitalOcean migration #77
Comments
This was referenced Oct 2, 2019
Closed
guylepage3
changed the title
Setup new express server for migration
Setup new Express server for migration
Oct 2, 2019
Not sure we need to do this actually. Loads of articles on deploying node.js / react apps to digital ocean. |
Reopening this issue. |
guylepage3
changed the title
Setup new Express server for migration
Pull out Express server for Digital Ocean migration
Oct 14, 2019
guylepage3
changed the title
Pull out Express server for Digital Ocean migration
Pull out Mailchimp Express server for Digital Ocean migration
Oct 14, 2019
guylepage3
added
refactoring
Refactoring related item(s) and issue(s)
and removed
coding
General coding item(s) and issue(s)
labels
Oct 15, 2019
guylepage3
added a commit
to universelabs/universe-email-subscriptions
that referenced
this issue
Oct 15, 2019
Signed-off-by: Guy Lepage <guylepage3@gmail.com>
guylepage3
added a commit
to universelabs/universe-email-subscriptions
that referenced
this issue
Oct 15, 2019
Signed-off-by: Guy Lepage <guylepage3@gmail.com>
Done. |
guylepage3
added a commit
to universelabs/universe-email-subscriptions
that referenced
this issue
Oct 15, 2019
Signed-off-by: Guy Lepage <guylepage3@gmail.com>
This was referenced Oct 21, 2019
guylepage3
changed the title
Pull out Mailchimp Express server for Digital Ocean migration
Pull out Mailchimp Express server for DigitalOcean migration
Oct 21, 2019
27 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As a result of migrating to a VM, we should pull the Mailchimp (subscribe) Express server out of the web app so that we can run them individual, separate services.
Tasks
The text was updated successfully, but these errors were encountered: