Fixed #19697 -- Added a deployment checklist. #913

Closed
wants to merge 1 commit into
from

1 participant

@aaugustin
Django member

No description provided.

@claudep claudep commented on the diff Mar 17, 2013
docs/howto/deployment/checklist.txt
+notify you accordingly.
+
+:setting:`LOGGING`
+------------------
+
+Review your logging configuration before putting your website in production,
+and check that it works as expected as soon as you have received some traffic.
+
+See :doc:`/topics/logging` for details on logging.
+
+:setting:`ADMINS` and :setting:`MANAGERS`
+-----------------------------------------
+
+:setting:`ADMINS` will be notified of 500 errors by email.
+
+:setting:`MANAGERS` will be notified of 404 errors.
@claudep
Django member
claudep added a line comment Mar 17, 2013

...when BrokenLinkEmailsMiddleware is enabled.

@aaugustin
Django member
aaugustin added a line comment Mar 17, 2013

Sorry, I missed your comment before committing :(

I intentionally left this detail out and linked to the full docs to avoid duplicating information (maybe that's dumb).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@aaugustin aaugustin closed this Mar 17, 2013
@mjtamlyn mjtamlyn commented on the diff Mar 18, 2013
docs/howto/deployment/checklist.txt
+you use a wildcard, you must perform your own validation of the ``Host`` HTTP
+header, or otherwise ensure that you aren't vulnerable to this category of
+attacks.
+
+:setting:`CACHES`
+-----------------
+
+If you're using a cache, connection parameters may be different in development
+and in production.
+
+Cache servers often have weak authentication. Make sure they only accept
+connections from your application servers.
+
+:setting:`DATABASES`
+--------------------
+
@mjtamlyn
Django member
mjtamlyn added a line comment Mar 18, 2013

Is it worth mentioning here that you shouldn't be using sqlite in production?

@aaugustin
Django member
aaugustin added a line comment Mar 18, 2013

Well, it's difficult to say something short and correct without losing generality, so I avoided the issue entirely.

If you don't put the sessions in the database, SQLite can take you quite far (1M pages / day sounds possible) on a read-mostly website.

There's certainly something to be said about using the same database in dev and prod, and preferrably not SQLite for websites that may receive non-negligible traffic or where data integrity matters. I feel that the deployment checklist isn't the right place for this digression. The databases docs seem more appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment