Move to Cloud: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) No edit summary |
Adamcolton (talk | contribs) |
||
| Line 26: | Line 26: | ||
# Confirm everything is up, running and works | # Confirm everything is up, running and works | ||
# Transfer domains | # Transfer domains | ||
==Also try== | |||
*Put the database (data) on a separate EBS volume | |||
*Try running that volume on a separate instance (one for apache, one for MySql) - this would allow a lot of scaleability | |||
[[Category:Projects]] | [[Category:Projects]] | ||
[[Category:Code]] | [[Category:Code]] | ||
Revision as of 20:29, 7 February 2012
I'm giving serious consideration to moving my sites out to AWS. To have a tiny instance running 24/7 will cost $105.
Setup
One tiny instance will run all the live sites, another tiny instance will be used for development. This will also host a Git server.
Comparison
Advantages
- Faster (this is a big problem with D5)
- Scalable (but do I really need this)
- Isolated Dev environment (and stage if I ever need)
- I can run whatever I want (Git, Postgre, Python, Java)
Disadvantages
- Cost (though in reality, I'm already paying this much because of the stupid 'privacy' thing that got turned on'
- Steep learning curve
- I will have to transfer all my sites
- There is a lot more room for me to screw up
Plan
- Get a tiny instance up and running with a lamp stack
- Buy a test domain from Amazon and get that hooked up
- Terminate it and make sure the EBS volume sticks around
- Reattach the volume to a new instance
- Try attaching the volume to larger instance.
- Transfer the sites over (data)
- Confirm everything is up, running and works
- Transfer domains
Also try
- Put the database (data) on a separate EBS volume
- Try running that volume on a separate instance (one for apache, one for MySql) - this would allow a lot of scaleability