Commit graph

9 commits

Author SHA1 Message Date
fa7f227318 Eliminate "conservancy" and "apps" subdirectories
The directory nesting is unnecessary here and confusing to navigate. I've moved
all apps to the project subdirectory, currently called "www", but soon to be
renamed "conservancy".

I've also moved manage.py to the top-level directory.
2023-10-25 12:36:39 +11:00
8058d768fb Add support for Debian Bullseye
Added `on_delete` attributes, updated ForceCanonicalHostnameMiddleware for
compatibility and added Dockerfile for Bullseye.
2023-09-12 10:59:45 +10:00
82d513b5b7 Apply pyupgrade --py36-plus (but skip f-strings as we're on Python 3.5) 2023-09-07 23:15:48 +10:00
98fcf8e35d Remove use of python3-future 2023-09-07 22:59:23 +10:00
49eff7af79 Apply "object" changes only from futurize --stage2. 2021-11-26 13:49:40 +11:00
a3626b18fb Apply futurize --stage1 (safe) Python 2/3 compatibility changes. 2021-11-26 13:00:20 +11:00
Tom Marble
2bf594b86c First pass at migration to Django 1.7 2015-03-03 18:40:18 +00:00
Bradley M. Kuhn
1e119efb7a Incorporate conservancy_ssl middleware, etc. into main site, now that HTTPS fully supported.
Previously, SSL on sfconservancy.org was supported using a self-signed cert
only to handle the /admin/ portion of the site.  Now that SSL is supported
site-wide, and perfectly mirrors the content available via HTTP, the
conservancy_ssl middleware, URLs, and settings are wholly deprecated and
herein removed.

The main site's urls.py now need adjusting to support /admin/, but additional
code is needed in middleware.py to avoid accidentally serving /admin/ via
HTTP instead of HTTPS.

The latter code is untested; hopefully it works "out of the box". :)
2013-04-26 13:09:24 -04:00
Bradley M. Kuhn
bd6199f7b0 Added middleware and management file 2010-09-26 19:03:53 -04:00