For what it's worth, you can cap your usage on Heroku, so any exceeded usage will just result in slow application rather than additional fees. For a small application with minimal traffic, a database, basic monitoring etc, you're looking around $40/month all in. Heroku is *not* a viable long term solution for growth, as the pricing really does become ridiculously high, but it'd perfect for small projects with low traffic projections and small budget :)
Cal On Wed, Dec 17, 2014 at 12:27 AM, Sayth Renshaw <[email protected]> wrote: > > Definitely Thanks Cal. > > Hadn't realized that with digitalocean. Been spending my time in ipython > and R and plotly and wanted to get some stuff out there. > > Rails not really in the equation too much black magic. > > Saw pythonanywhere, Heroku, Bitnami they just don't have a fixed cost. Eg > Bitnami says about $6.95 a month but it's about. I do something random abs > could cost myself a bucket. > > Sayth > > On Wed, 17 Dec 2014 11:14 AM Cal Leeming <[email protected]> wrote: > >> One thing to note, DigitalOcean is truly awesome but it is a no-frills >> service. You get an API and raw performance at dirt cheap pricing, >> everything else you have to handle yourself. >> >> If you don't have the necessary devops/sysadmin skills, e.g. knowledge of >> how to recover crashed databases, corrupt filesystems etc, then you might >> want to consider something like Heroku where you can leverage the power of >> build packs. This can get *very* expensive, very quickly, but for small >> databases and minimal throughput, you'll be fine. >> >> To be clear, I don't want to put you off using DigitalOcean because I >> honestly think they are the best thing to happen to the unmanaged hosting >> industry in a long time. At the same time, you should be aware that this >> cheap, raw performance comes with a trade off. If you want to push and >> forget, use Heroku. But if you want excellent performance, low pricing and >> complete control, look at DigitalOcean + Packer + CircleCI. (you can push >> to git, which then triggers a CircleCI build, which then triggers a packer >> build, which then spins up a new VM at DO on that snapshot. However you >> then need to handle destroying old instances, and automating the switch >> over between instances, which would need to be some sort of LB or DNS >> change over using something like CloudFlare). It gets pretty intense :) >> >> tl-dr; Deployment of Rails vs Django has the same considerations and >> complexities. You'd have to consider the above no matter which you use >> anyway. >> >> As for which would be more preferable, that comes down to personal taste. >> My advice would be to review them all, pick two or three, and see which one >> excites you the most. >> >> Hope this helps dude! >> >> Cal >> >> On Wed, Dec 17, 2014 at 12:03 AM, Sayth Renshaw <[email protected]> >> wrote: >> >>> Wow never knew mezzanine existed, that's interesting. Yes php hosting is >>> cheap, but so is digitalocean and it fully supports python and django. >>> >>> Sayth >>> >> >>> -- >> >> >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >> >> >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-users/e2a68abd-1e64-4e28-bedb-3fe8cb2bae62%40googlegroups.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Django users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/django-users/NmnbelIldz8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CAHKQagGsZLaGjJEaSC1StTVPeMdCxW7h%3D5XzNk-pLYRRf2ccFw%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-users/CAHKQagGsZLaGjJEaSC1StTVPeMdCxW7h%3D5XzNk-pLYRRf2ccFw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAN2of00-OZLLg7b7NOnexUWoHyw12EvBJEYbXdZmq-ZmmjpHUw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAN2of00-OZLLg7b7NOnexUWoHyw12EvBJEYbXdZmq-ZmmjpHUw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHKQagGL7%2BOXv4_zgKAFs7sWkWZTaywmhgWtF%3Dx_DgMG_EdwCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
