We don't have these mini-confs (yet).
We don't want these files.
We're not going to rename the release in 0010 and drop all the extra
tables in 0011, we're going to toss them on the cutting room floor and
call it good.
They're in git, we can look at this commit and past ones on how to
recreate these for new proposal additions going forward.
This causes template rendering to blow out of proportion on certain
views. I don't care enough about this feature to spend time fixing it.
It has not provided me any value to this point.
One such view is ^/tickets/profile$ however there are others where I saw
this, yet do not remember which ones they were.
This field is ignored in 1.9, however in 1.10+ it is an error.
As this is a no-op in 1.9, removal keeps functionality while
extending compatability going forward.
For full details please see Django Ticket 10414 at:
https://code.djangoproject.com/ticket/10414
This removes images, and giant headers, and makes the text - not white.
The next layer down in CSS is blue, so that's it for now.
This helps understand what's on the page visually, so this, at the
least, make testing easier for now.
This should eradicate wagtail from the project.
While wagtail may be nice, our goals are to keep all things public, and
having things locked behidn a DB is congruent to that plan.
All in all, the django project only leveraged a single wagtail feature,
"richtext" which has been hacikly removed and will result in bad display
of however it comes up. But this is on homepage.html, which will be
removed and covered up with a static website, which means we should be
able remove homepage entirely from this project.
This reduction hopefully makes the monolith easier to understand,
maintain, and wield.
While 1.7.0 exhibits a similar issue, we would need to re-verify and
re-patch this library with a new 1.7.0 monkeypatch.
This is ultimately only an annoyance. It only occours when we've
already 500'd, and this just means we get a second 500. As such it's
not critical.
Boxes takes content directly from the DB and drops it into the django
templates. This is rather ugly and goes against keeping as much as we
can in static locations. As such, this is being dropped.
Works in prod mode, dies in dev with a warning/error
Doco seems to suggest that mixing these directories together is an
error as it means user uploads mingle with site files.
- remove a whole bunch of comments, they're useless
- Update TimeZone to Sydney
- Don't colocate MEDIA (user uploads), with STATIC in fact,
how is this set, Django has a safety check for this and bails.
- Do not store a default SECRET_KEY in git.
We'll set a random one by default, so things "just work"
It would also be acceptable to not set it and let DJ bail
- We dont want to log to a file. Our disks are ephemeral.
- We likely will not overlay a production settings.py over this one.
We need to implement something that is more container friendly in the
future. This will be env-vars or a config file.
This only seems to be here to have some custom login_url used bypassing
django's model. Well as we want to use django's model, this just won't
do. So lets move to using django's model.
In the future, when we want to lock a package to a specific version, we
will do that via a constraints file in the master project.
Making it difficult to update deps is not okay.
