11–20 of 28 posts
Very cool! The one-click setup blew my mind. The only other thing I would expect with this is some kind of vcs integration, like git integration.
So in the case of git, you can keep using VCS just like before - place your local files in a repo and use the Github app / command line. Our goal is for you to continue to use the workflow you're used to.
Overall its a great concept and something I think you'll see done by companies like Heroku as a form of lock-in as teams grow and never really learn how to virtualize their workflow. If you can get on the front of that movement it will be interesting to see where this project goes.
Good Luck!
Looks slick, but how is this different from just running "django-admin.py startproject mysite"? When developing something serious, you typically want to match the stack you will be deploying on. So far, the two easiest (not necessarily wisest) options have been Google App Engine and Heroku, with latter being my choice of late due it running on AWS and "closeness" to S3 and DynamoDB.
If multiple developers can modify files at the same time, how do you handle merge conflicts when syncing?
Looks slick, but how is this different from just running "django-admin.py startproject mysite"? When developing something serious, you typically want to match the stack you will be deploying on. So far, the two easiest (not necessarily wisest) options have been Google App Engine and Heroku, with latter being my choice of late due it running on AWS and "closeness" to S3 and DynamoDB.
Our video is indeed starting a django project for you - we take a step further and let you do that in a click without having to set up a virtualenv, and it's all hosted. This is the basics, but the idea is to move your development onto a hosted server that is the same or much closer to your prod environment.
Ideally, this hosted environment can offer you much more than what you get by installing a different version of everything you’ll be using in production onto your laptop.
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 user…
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.
First off, very cool! Nice work. If multiple developers can modify files at the same time, how do you handle merge conflicts when syncing?
At this point we're not focusing on collaboration between developers. There are incredible companies like GitHub whose core mission is to make code collaboration an amazing experience, and we really want to help developers leverage this while not worrying about environment, config & setup issues.
Thanks for the comment!
Your clean page, and the design and colors of your icon led me to think at first that this was a google project.
Compare your logo to that of google play's logo.