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

Transfer makes.org to Heroku and decommission AWS infrastructure #204

Closed
jbuck opened this issue Oct 2, 2015 · 3 comments
Closed

Transfer makes.org to Heroku and decommission AWS infrastructure #204

jbuck opened this issue Oct 2, 2015 · 3 comments
Assignees

Comments

@jbuck
Copy link
Contributor

jbuck commented Oct 2, 2015

@cadecairos already did the work to get make-valet working on staging, so we just gotta get production working and then decommission the AWS infra!

@jbuck jbuck added this to the Spooky Scary Skeletons milestone Oct 2, 2015
@cadecairos
Copy link
Contributor

makes.org and mywebmaker.org are both on Heroku now. Staging is on the free teir, production is on a single 1x dyno ($25), and both are running heroku SSL ($20x2)

I've scaled down the staging and production autoscale groups to zero.

We'll wait 24 hours just in case any problems surface, then take destroy all the AWS resources associated with make-valet.

@jbuck
Copy link
Contributor Author

jbuck commented Oct 2, 2015

Thanks @cadecairos !

@cadecairos
Copy link
Contributor

Decommissioned Infrastructure

Auto Scale Groups
  • makevalet-production-as
  • makevalet-staging-as
Load Balancers
  • makevalet-staging
  • makevalet-production
Launch Configurations
  • makevalet-production-64-newrepo
  • makevalet-staging-64-1b
  • makevalet-production-64-newpuppet
Security groups
  • makevalet-ec2-sg
  • makevalet-ec2-sg-v
Keypairs
  • makevalet-130704

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants