But even more importantly, think how you could automate all this:
https://github.com/mhoofman/wordpress-heroku
https://github.com/mhoofman/wordpress-heroku
Save money on hosting today!
- Thread starter mattseh
- Start date
I tried that a few months ago with a bunch of installations. It's pretty damn simple when it comes to regular old sites and if you wish to replicate existing, preset customization.
However that thing is a bitch for customization - there is practically no scope for trial and error. You have to finalize all customization offline and then push them to the cloud (which may or may not be a good thing).
However that thing is a bitch for customization - there is practically no scope for trial and error. You have to finalize all customization offline and then push them to the cloud (which may or may not be a good thing).
You can run a local install if you really don't want to commit everytime you want to test something
Heroku is so dope.
I host all of my applications (mostly Ruby) on it and use EC2 directly to host smaller services (like proxies and Solr/Sphinx search indexing).
People bitch about price, but trying to keep down costs has only led me to design better application code. Instead of spinning up another dyno, you think things like "can I cache this any better?" or "should I isolate this service on its own process?"
I host all of my applications (mostly Ruby) on it and use EC2 directly to host smaller services (like proxies and Solr/Sphinx search indexing).
People bitch about price, but trying to keep down costs has only led me to design better application code. Instead of spinning up another dyno, you think things like "can I cache this any better?" or "should I isolate this service on its own process?"
I find that the people who say it is too expensive full stop either don't value their time, or don't have enough margin built into their project pricing, or have rare special circumstances.
I really like how it is polyglot.