"In principle" setting `SCRIPT_NAME` is enough. The way we do this is [1] using
`FORCE_SCRIPT_NAME` (which does not depend on messing with reverse proxy
settings and [2] by deducing the correct value from `BASE_URL` (which must be
set anyway) automatically.
By works I mean: `reverse` and `{% url` pick it up from there.
However, there are subtleties / extra work:
* `STATIC_URL` is needed too b/c https://code.djangoproject.com/ticket/34028
* in many pre-existing code I just created a path manually in the html. Such
hrefs are obviously not magically fixed for script_name. Rather than doing
the "full rewrite" (into `{% url`) this commit just prepends the
`script_name` in those cases. That's the way forward that will least likely
break and it gives us something to grep for if we ever want to 'do it
right'.
* `LOGIN_REDIRECT_URL` and `LOGIN_URL` needed to use a view-name for this to
work (using a view-name gets revolved using the thing that introduces
`script_name`)
Checked, no work needed:
* views (`redirect` and `HttpResponseRedirect`)
* html uses of action="..."
Fix#93
* in 1abc30a760 the hardcoding of ="dark" (during development)
was accidentally checked in; it never should have been.
* in e14b3eaaa6 I mixed up the bare*base templates. It's actually
bare_base.html that's for 404/500 etc; barest_base is more bare
visually (it's the box-based layout for login etc), but it doesn't
need to be so careful not to use variables.
See #40
my chatbot tells me it felt ugly because
> bg-yellow-900 [..] is a very saturated, reddish mustard — almost
> brown-orange. That’s why it feels so jarring in dark mode: it's too warm,
> too saturated, and clashes with a cool-dark UI. [..] Try bg-amber-800
> instead. Tailwind's amber palette is warmer and more muted than yellow,
> designed to fit better in dark UIs.
No idea if the reasoning is sound, but it "looks good" so I'm pushing ahead.
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.
> The tag generates a preload directive for your stylesheet, which improves
> loading performance in production. Place it above the {% tailwind_css %} tag:
See e.g. https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel/preload
For a brief moment I thought that this was malfunctioning, because it is missing
the ?v=... part, but that part is DEBUG-only, so we don't care about it for real
use-cases
Klaas van Schelven