DEBUG is something that should never be turned in on prod. As such,
lets be extremely specific on what we expect to process.
As we'll be taking this in from the environment, it's ensured we will
get a string. So we'll always get and only handle this in string
form. If it's anything else, it's an operational error and we bail.
(Note: bool('0') is truthy, so we make sure we leverge our string -> int
-> bool every time, so corectness can be noticed if it is not)
Remove in-app stale resources and their branching of different cons.
Remove dist and move everyting into static/src.
Remove unused stale resouces such as less and hbs, etc.
I cannot find the benifit to this over the base editor.
Tabs work, but that's pretty minimal. And tabs don't work on GitLab or
GitHub, so I don't feel not having that is substantual to functionality.
The bootstrap renderer did not do anything to signify required rows. We
can do this by adding a class for CSS to work on, and add this field in
a more simplified manner.
label-required == append ' *'
I'm not against putting this back, however, it doesn't work quite as one
would expect, so I'm removing it as its functionality is more confusing
that working.
Is this really the best way to address this?
If you unselect AU, then it never comes back. It leaves its value in
the textbox pre-filled if it ever got a value, leaving the field
pre-filled with an Aus state even if the person is New Zealand.
Most of our attendees are from but a few countries, we should make these
equal effort to fill in.
Boot custom CSS, and put some base, standard css in its place.
Shame I did not start with fresh Bootstrap4, but oh well.
Some more templates could be made to make this less messy, which would
be good.
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 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.
Removed additional (and completely superfluous) styling in app.css that was otherwise making
our site look gluggy.
Mod'd fixtures (and updated db) to reflect PyCon rather than PinaxCon.
Nearly there. Much rubbish / cruft ripped out of site_base.html and content_page.html.
Had to modify cms_pages/models.py to accommodate a "simple" layout option in the homepage
editor.
Still some stuff to do. Styling not quite there yet, but want to checkpoint this.
* Adds schedule fragment script
* removes spurious logging
* Displays the right tab on DOM load.
* Load today’s schedule if we’re during the conference.
* remove TODO
* Optional track name with room name on schedule, access schedule by day eg /schedule/?day=Monday
* Changed to using a Track model rather than a char field
