I'd like to illustrate why I think having official documentation about
deployment on PaaS would be great.
What I mean by "there is confusion", is that IMHO on a PaaS SECRET_KEY
should be managed by settings.py in an automatically created file in a
private and persistent directory.
For example:
Pretty nice docs they have nowadays I recon !
Perhaps we don't need documentation for all open source PaaS out there
(ie. DEIS, the open source heroku-ish PaaS for CoreOs). Having at
least one could help though.
The only documentation about deploying django apps is in their blog
and it's not
I don't mind maintaining the instructions for these common platforms and if
Django's docs didn't have any deployment instructions that might be a bit
odd.
For what it's worth, the uwsgi docs do have some nice (at a very quick
glance) looking instructions:
Perhaps, should we also start moving mod_python / uwsgi docs upstream ?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Does OpenShift have some suitable docs you can contribute to? I don't think
the Django docs are the right place for specific deployment scenarios like
this.
On Tuesday, March 15, 2016 at 5:42:31 PM UTC-4, is_null wrote:
>
> Hi,
>
> OpenShift Origin is an Open Source PaaS system based on cool
Hi,
OpenShift Origin is an Open Source PaaS system based on cool stuff
like kubernetes, docker, ansible, golang ... developed mostly by
RedHat. It's probably comparable to Heroku, but more flexible and
completely Open Source (thanks RedHat !!).
I use OpenShift every day, including for a few open
