* The default is "localhost" now (as per what we write in the docs on the
website). (It already was the default for Docker, but not for all settings
yet)
* FREE_VERSION-nagging adapted accordingly
* create_conf: adapted accordingly.
* create_conf: Fix help-text ("BASE_URL" not "SITE_TITLE")
* deduce_allowed_hosts
* don't just generally accept "*" for the locally hosted one, instead
specify the 2 correct spellings
* "and vice versa" ("localhost" accepted in your browser bar if you specify 127.0.0.1)
during user-testing, it was revealed that people think there is something
wrong when they see 'DivisionByZero' when this is in fact precisely what
was intended. Hopefully the new text removes this confusion
As discussed in #11, there are scenarios (e.g. misconfiguration) where snappea
does not pick up the tasks. Events not showing up in Bugsink, w/o further
indication why that may be, leaves people confused. Better to warn explicitly
in that case.
prompted by the LHS going awry, esp. the part where the 'Show all' etc buttons
git commit -m "'Issue Key Info'; show on xl, not lg. (while recording a video
at 1080px width)
Fixes#7
I could not find any documentation on what the "standard" is, but I know that
we'll pick it up just fine either way (because Django's UUID field does the
magic for us).
Given that it's impossible to setup your JS client with the dashes, they should
simply be removed.
why: simply motivated by Python's own EOL-cycle; i.e. I'm not
actively going to use any 3.13 or 3.9 features now.
how: updating test-matrixes; but no actual local testing done yet
(this is the last version that supports Python 3.9, which we want to
support as it's not EOL for a full more year)
https://github.com/timonweb/django-tailwind/issues/210
Afterwards, I went through a full cycle of:
```
rm theme/static_src/package-lock.json theme/static_src/node_modules/ -rf
python manage.py tailwind install
python manage.py tailwind build
```
but this did not change any of our generated stuff.
in IMMEDIATE mode, project was passed from an (implicit) read transaction to
the immediate_atomic-wrapped code; this meant that it was possible to miscount
project.digested_event_count
