Re: Django hosting

Hi Sabine,
I use Redhat's Openshift.

On 25 Sep 2014 07:55, "Sabine Maennel" <sabine.maennel@gmail.com> wrote:

Thank you very much for your advice Marc, it is very valuable to me, especially the part that my hosting provider for today does not need to be that of the future. My problem right now is that I am under pressure to launch, but just in order to open up registration for a class that won't start before January 2015 where the real traffic will start. So I might not test thoughly now, and need a quick solution now, but then I will have two month to prepare for January and in case I am unhappy with the hosting I will still be able to change then.

           with kind regards and thanks again that you took so much time for that long informative answer

                 Sabine

Am Donnerstag, 25. September 2014 07:58:02 UTC+2 schrieb mark:

Sabine,

I am in the US, so take my advice with a large grain of salt. I usually use Linode and Digital Ocean as a benchmarks for hosting services. There prices are very reasonable and they give you all that you need - root shell access to your own private virtual server. They have great up-time, and my only complaint has been about their backup service, but then who would really trust a hosting company to back up your critical data??? Both can scale as you grow - increasing memory, disk space, bandwidth takes just a few minutes. Both have European data centers...Linode in London and Digital Ocean in Amsterdam.

Anyway, Pyrox seems very expensive, and Django Europe is much closer to Digital Ocean/Linode in price. I am not wild about the process limits at Django Europe...I tend to think about physical things - memory, disk space, bandwidth, etc. I am not a good enough sys admin to know which processes to kill, and the thought of not being able to log in because I am running too many processes is scary...check the FAQs at Django Europe.

If you have built your own django app for your start-up, I don't think you really need to pay for "instant-on" django a la Django Europe. You are quire capable of setting up your own Django production virtual server. Email and no phone is OK as long as you they have a guaranteed min/max response time. I assume you will be your own sys admin, so there is not much they can do for you anyway. Keep good backups and don't push to production until you have tested the heck out of your new code on a different, but identical, development server. Practice rolling back to an earlier release BEFORE you go live. If your site just dies, and you have good backups, you can create a new node, install from backups, change the dns on the local name servers, and you are back live in a few minutes. Then figure out with the hosting folks what went wrong and ask for a refund...;) 

Finally, you can get 2 Virtual Private Servers on AWS EC2 for free for the first year.  After that, their pricing is STILL cheaper than Linode or Digital Ocean.   But you will have to investigate that by setting up mockup billing as you build your systems and evaluate your needs.  You have a whole year.  Their free tier includes a good amount of startup resources: http://aws.amazon.com/free/. Also, your hosting provider today may not be your hosting provider tomorrow....start free, learn what you need and how much you need to scale up, and then move to paid hosting. AWS EC2 also has European data centers.

Anyway, just my 2 cents on hosting. Lots of options.

Mark

On Wed, Sep 24, 2014 at 8:40 PM, Sabine Maennel <sabine....@gmail.com> wrote:

I live in Switzerland and I will launch my startup shortly. It will be a very small platform in the beginning but traffic might grow all of a sudden. So regarding to hosting I am torn right now, between Pyrox, which is a small, but accessible Germ hoster and Django Europe, which is spezialized on Django and LightTTPD. They offer a one click Django install, but no phone support only tickets. Can anyone give me advice regarding hosting? Has anyone used on of these two hosters? 

         Thanks in advance for your advice

                  Sabine

--
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 django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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/9efbfc90-c92e-4914-afca-f39b9dee5c6a%40googlegroups.com.
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/7b99ef07-87ac-4719-a592-f8a29c236776%40googlegroups.com.
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CA%2BWjgXM_CUU13pN01vdJQojjHKa9p_hMyRcgErQjZg55b9NFwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.