Great idea on deployment, wish I had said the same. PaaS's are great but if there was officially supported boilerplate for supervisor/gunicorn/uwsgi/nginx/postgres, say, on Docker, that would make life terrific.

That's a great idea! An official docker (and/or AMI?) that has everything set up and optimized, and you just add your project to a specific directory!

Django could release and update with every release.

FYI some people are working on putting a (probably) docker image together for testing purposes. The point being that contributors can test their changes to all backends on their own terms.

I'm hoping it won't be too hard to add a deployment story at the end.

Deployment is a pain. Perhaps some official tutorials would be good in the interim.

An official tutorial would be great in any case, with or without an accompanying Dockerfile!

There is an Apache/mod_wsgi image from the mod_wsgi maintainer. It was pretty easy to set up, and Graham has more in depth documentation on his blog.

https://github.com/GrahamDumpleton/mod_wsgi-docker

I've been evaluating using uwsgi as a stand-alone server. I'm not sure how much load it would support, but I think it's possible get quite far with Django, sqlite, and uwsgi.

Here's an example of a run of the mill 'nginx', 'gunicorn', 'supervisord' setup: https://github.com/Pakebo/eb-docker-django-simple/blob/maste...

Easiest way to improve the production deployment situation is to use a PaaS like Heroku. Something like Dokku may simplify things by having all the "wiring" done for you. YMMV.

Thinking about it a bit more, there could be less directory settings in Django itself. Maybe there could be more "convention over configuration" outside Django too. I do remember it being a pain doing it first time since you don't know where all the log files are.

I disagree, I have had more hassle getting stuff to work on Heroku than from a bare VM. And debugging is far more hassle as well.

I mentioned the admin interface as well. I wish it was easier to customise when you need something more user friendly, and not something that is just a GUI for accessing the database. But it is hard to get away from, since everything else by default plugs into it.

After customizing the admin interface so that it could be used by the staff of a couple of organizations I wrote web sites for, I realized that it's much easier to write normal views for this. It's simple to use decorators to enforce staff logins on views. Really customizing the admin becomes pretty tortuous pretty fast. However, it's great to have available as an interface to the DB for the developer; not so much for the users.

Don't mind my personal plug, but you might be interested in taking a look at Smartmin: https://smartmin.readthedocs.org/en/latest/

(don't mind the stale release, just use master)

It is a much, much better admin-like tool to use for building CRUD views, with strong conventions on permissions, URL structures and template names. It really simplifies things and we've been using it internally for four years on a dozen different projects.

Can't imagine using Django without it.

Sounds neat but I'm having trouble figuring out what it does. Maybe you could include screenshots, and simple sample code showing how it's used?

I will also have to write normal views for it. I just would like some easy system for pluging those views all together nicely for, without having to do it myself. Also some extra stuff to take care of permissions when doing that. I eventually I think I will have to write my own such system to get what I want.