[sologoub]

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.

[jeffdm]

Sorry for the delay in answering and thanks for the comment. This is a good question.

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.

[sologoub]

Thank you for the clarification. It appears my confusion stems from me doing similar workflows, just with existing tools - when I tinker with either GAE or Heroku, I deploy nearly continuously, which achieves the same results, but on the exact infrastructure that the final version will be deployed on.

I definitely see the benefit for those not utilizing such practice already.

[sologoub]

Down vote and no comment - what's offensive in not understanding a significant value add?