[dhrp]

I think this is pretty cool.

As a front end developer I would like to see this mature into a project which "makes my life easier", and currently, one of the biggest pains, I think is setting up a nginx or apache project with the right WSGI directives.

What I would love to see this develop into is a way to get my code pretty much straight from my IDE to a server of my own (whether hardware or virtual). I know it is very limited in deployment features right now, but I can pretty much rely on Docker to do that. e.g. "sandbox build /folder"; docker push dhrp/folder; ... ssh to my server ... docker run dhrp/folder. Done!

Two things are still missing here: * Some kind of proxy with virtualhosts to map port 80 to my container * A default run command for container committed by sandbox

[StavrosK]

Try this:

http://www.korokithakis.net/posts/example-provisioning-and-d...

You can go from fresh installation to complete Django stack in one command.

[dhrp]

Right. I can write a script to go from fresh installation to deploy in one command using Vagrant, Puppet, Chef, Ansible.

But the reason why so many people like PaaS such as Heroku and dotCloud is actually that there is /one/ recommended way to structure your app (at least, what to put in wsgi and so forth). It's about making it easy to go from code to package to deployment.

[shykes]

Note that docker supports both allocating your port 80 to a container ('docker run -p :80'), and setting a default command to run.