Ok, yes. True on the time costs. I'm a new developer (3-4 months) and I swear (sometimes) I spend 55% deploying and 45% developing.
On Tuesday, March 25, 2014 6:49:11 PM UTC-6, Kenneth Bolton wrote: > > I run Mezzanine on variously sized EC2 instances as well as on a > RackSpace, nee Slicehost, VPS. A EC2 micro instance is free for the first > year, but generally costs less than $10 per month. Digital Ocean, at $5 per > month, also worked well for me the very first time. I have used the > included Fabric script to build and deploy to the aforementioned with no > modification. > > The real cost is not the monthly hosting cost, but the development, > deployment, and maintenance costs. If you have spent more than an hour > working on your deployment, you have cost yourself several months of > hosting expenses. > > ken > > > On Tue, Mar 25, 2014 at 8:27 PM, Kyle Pennell <[email protected]<javascript:> > > wrote: > >> How much harder is it to use Heroku vs. GAE? >> >> >> On Wednesday, April 10, 2013 4:05:07 PM UTC-5, Nate Aune wrote: >>> >>> I wanted to let folks on this list know about a new deployment tool that >>> I've been working on called django-deployer. >>> http://natea.github.io/django-deployer >>> >>> Here is a short 5 minute video showing how to deploy Mezzanine to Google >>> App Engine, with instructions on how to set up your Mezzanine-based project >>> on App Engine and Cloud SQL. >>> http://appsembler.com/blog/deploy-django-apps-to-google- >>> app-engine-with-django-deployer-in-5-minutes/ >>> >>> django-deployer is essentially a fabric script that automates the >>> creation of all the configuration files necessary to deploy your Django app >>> to any of the PaaS providers. Currently there is support for Dotcloud, >>> Stackato and Google App Engine, but there are plans to add support for >>> Heroku, OpenShift and Gondor as well. >>> >>> When you run the script, django-deployer asks you a series of questions >>> about your project and writes the answers out to a deploy.yml file. The >>> hope is that in the future, you could stick a deploy.yml file in your >>> Github repo, and any of the PaaS providers could consume this yaml file and >>> translate it into their specific way of deploying your app. Until then, >>> django-deployer is the babelfish that does that translation for you. :) >>> >>> While the script works mostly as advertised, it's very much still an >>> alpha quality piece of software, and I consider it a work-in-progress. If >>> you want to try it out, I'd love to get feedback on how it can be improved. >>> >>> Nate >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
