[d0m]

Love it, this is great. I'd definitely use it for quick prototypes and hackatons.

It says "No setup, No configuration". But what if I want to configure stuff? For instance, there's a lot of things going on in settings.py.. to name a few: - setting up the DB - email config - celery (tasks and stuff) - Caching

How much control do I have on the "cloud"? I.e. if I want to create a folder to put the files uploaded by users? If I want to run background tasks?

Also: How does one switch from dev to production? Does Kite plan to offer a robust solution for production down the road? I'm not overly concerned because since I have a local folder, I can easily deploy it to any vps.

I have dozen of django projects and I'd gladly give it a fair try, let me know: phzbox at gmail.

[jeffdm]

Thanks!

We wanted zero setup for devs who may just want to get something up and running right away. The video shows the basics, and we definitely realize there is much more to building a web app than that.

We want to make configuring your app and using common services easy without Kite getting in the way. That’s our mission. Although we showed direct shell access to your app in the video, our end goal is to give developers a machine they can call home as their development environment - root access and all.

For databases, we’re making it a simple click to bind a database to your app. Similar to Heroku, we plan to expose different options as a service and they will be connected to your app through the dj_database_url python module (for Django). For beginners, we’ll try to edit your settings to help make this seamless (your settings.py files in this case).

For other services such as email, task queues like Celery, memcached, etc. we plan on taking a similar approach - offer it as a service on a separate machine that can be easily added to your app, or alternatively just install it in your environment if its something very lightweight or serverless (like sqlite).

Like other hosting services we’ll provide storage for things like storing user media, static files.

We’re really aiming to start with development, since there’s this large gap between development and prod that creates serious time-wasting problems that each member of our team has felt. Companies like Heroku are solving the production problem very well, but developers are still left to setup their own environment and deal with problems leading up to prod.

That being said, we see the serious benefit in using the same stack for development & production, and, like others have mentioned, testing, staging, CI. It’s definitely on our mind, and we’d love to see this kind of fragmentation disappear.

Great to see that you’re interested, and we’ll definitely be following up with you soon.