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

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants
Owner

aaugustin commented Mar 17, 2013

No description provided.

+
+:setting:`ADMINS` will be notified of 500 errors by email.
+
+:setting:`MANAGERS` will be notified of 404 errors.
@claudep

claudep Mar 17, 2013

Member

...when BrokenLinkEmailsMiddleware is enabled.

@aaugustin

aaugustin Mar 17, 2013

Owner

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).

@aaugustin aaugustin closed this Mar 17, 2013

+
+:setting:`DATABASES`
+--------------------
+
@mjtamlyn

mjtamlyn Mar 18, 2013

Member

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

@aaugustin

aaugustin Mar 18, 2013

Owner

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