Merge lp:~james-w/pkgme-service/log-oopses into lp:pkgme-service
Status: | Merged |
---|---|
Approved by: | Jonathan Lange |
Approved revision: | 40 |
Merged at revision: | 39 |
Proposed branch: | lp:~james-w/pkgme-service/log-oopses |
Merge into: | lp:pkgme-service |
Diff against target: |
145 lines (+69/-3) 9 files modified
.bzrignore (+1/-0) dev_config/templates/production_credentials.cfg.erb (+6/-0) django_project/dev.cfg (+6/-0) django_project/main.cfg (+35/-0) django_project/production_credentials.cfg.example (+6/-0) src/djpkgme/templates/404.html (+5/-0) src/djpkgme/templates/500.html (+5/-0) src/djpkgme/urls.py (+1/-0) src/djpkgme/views.py (+4/-3) |
To merge this branch: | bzr merge lp:~james-w/pkgme-service/log-oopses |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Lange (community) | Approve | ||
Review via email: mp+89999@code.launchpad.net |
Commit message
Add the configuration to have django errors logged to a file.
Description of the change
Hi,
This adds the configuration for django's logging framework to log
everything at WARNING or higher to a log file.
It also does a couple of things that will help with using this:
* Adds /pkgme/+oops URL that generates an exception on purpose.
* Adds a template for 404 so that they don't turn in to 500s
* Adds a template for 500 so that we know what the real exception is, not
the one that says "You don't have a 500.html template."
This will require some co-ordination with IS around deployment so that the
config is in place first, and the config needs to be created by puppet
so that it can point to the right log dir. I'll propose a branch to add
this to the template.
Thanks,
James
Looks good.
Why do we set the log dir for Django in the example credentials, but set the output directory for pkgme in the production.cfg?
Is there some wiki page we should update for tricky deployments?