I'm personally a big fan of the single-server setup, but the reality is that a lot of
people like Docker, and we don't want to scare people away from the Docker setup either
(especially since it's pretty good these days)
We don't use fastjsonschema's exception info, falling back to jsonschema for that. Not using the info is faster.
Possible because https://github.com/horejsek/python-fastjsonschema/issues/187 was completed.
I did not at present do any speed/memory checks, but the diff is quite promising :-)
Reverts part of 8ff309cd8f7a; in that commit I was inspired by the comment
right above it to make it more strict, but taking a step back (and inspired
by a user tripping over ALLOWED_HOSTS validation) defaulting to "*" for
basically non-configured setups is actually better.
Preserved from 8ff309cd8f: the idea that both 127.0.0.1 and localhost are
seen as localhost.
Mysteriously, "Truncated incorrect DOUBLE value". But we have no Double fields.
Answer: adding a value to a field (with "+") tries to convert to Double first
on MySQL. Using Concat solves it.
Showed up in all paths exept "resolved by next".
Fix#14
* 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.
