Stable - Badass Python web hosting (coming soon)(stable.io)

13 pointsby stevelosh16 anni fa7 comments

Stable - Badass Python web hosting (coming soon)

http://stable.io/

4 comments

Are you going to provide PostgreSQL access? If so, are you going to run a shared database? What about database quotas, are you solving it on a file system level?

Are you going to use mod_wsgi, nginx/gunicorn, or something else?

How are you building/scaling/deploying the presumably virtualized servers needed to host users apps? Puppet, Chef, Fabric, or something else? Are you running on EC2?

Will there be file system access or only read-only access like Heroku?

How will you compete with djangy.com and other services which are in the works? (you already seem to have an advantage by not running in debug mode....: http://news.ycombinator.com/item?id=1617691 )

How are you going to handle mail delivery? Through a third party over HTTP?

What about DNS? Will you allow A records or just CNAME records like AppEngine?

Looking forward to try the service out, but I'm not sure it will be much easier than my current Puppet setup:

    gunicorn { "murerknutsen":
      domain => "murerknutsen.no",
      django => true,
      postgresql => true,
    }

(cross post from http://forr.st/~XTn )

stevelosh16 anni fa

Cross posting reply from Forrst :)

    Are you going to provide PostgreSQL access? If so, are you going to run a shared database? What about database quotas, are you solving it on a file system level?

Yes, PostgreSQL. Shared-only during the beta, then later we'll offer dedicated DB servers of various sizes.

    Are you going to use mod_wsgi, nginx/gunicorn, or something else?

Nginx + one of gunicorn, uwsgi, or gevent. We're still evaluating the different options.

    How are you building/scaling/deploying the presumably virtualized servers needed to host users apps? Puppet, Chef, Fabric, or something else? Are you running on EC2?

Fabric at the moment, but I hope to find some time to learn Puppet during the near future. And yeah, EC2 just like Heroku.

    Will there be file system access or only read-only access like Heroku?

Read-only, like Heroku. It's safer and not too difficult to work around in your apps.

    How will you compete with djangy.com and other services which are in the works? (you already seem to have an advantage by not running in debug mode....: http://news.ycombinator.com/item?id=1617691 )

We're not focusing on Django-specific deployment -- we're going for a broader target by offering WSGI hosting (which includes Django, of course).

And we have a kick-ass designer to make our user interface and documentation look good. UI matters.

    How are you going to handle mail delivery? Through a third party over HTTP?

We're not touching email at all. If you want to send email, use Postmark. To get email, set your MX records to some mail host (like Google Apps).

Email is complicated and orthogonal to hosting.

    What about DNS? Will you allow A records or just CNAME records like AppEngine?

We're still working on the DNS setup.

    Looking forward to try the service out, but I'm not sure it will be much easier than my current Puppet setup

Once you have Puppet in place then yeah, it's pretty easy to deploy Python.

What happens when your site hits the front page of Reddit? Can you add 5 Gunicorn workers quickly? What if you're not at your computer and want to do it from your phone?

edanm16 anni fa

I'd love a one-push deployment option for Python. But the website should really have some more details.

alialithinks16 anni fa

I agree... We will do that as we keep moving forward for sure.

beshrkayali16 anni fa

Would love it as well...

steyblind16 anni fa

What's the difference between this and regular web hosting?

What services compare to stable.io?

nicksergeant16 anni fa

One-push deployment and management.

http://heroku.com

steyblind16 anni fa

When are you guys hoping to drop something? 1 week? five months? fourteen years? ham?