TW
Creating a fake django_session table to make `dumpdata` happy: ``` create table django_session(session_key, session_data, expire_date); ```
That it generates a new secret when invoked is documented and IIRC also pointed out on the user interface. It can not show the configurations without access to a secret...
see also #303. yes, we could show a incomplete (without password) configuration without generating a new password.
asmaps wrote: CDN is good for now. For self-serving put them in static
if we just put it in static, we have 3rd party stuff in our project, not nice. so let's just use xstatic, it was invented just for that and is...
this task can be held back as long as we just use all 3rd party stuff from the CDNs. but as soon as we have a reason to serve that...
Yeah (although in that specific case they said that the CDN isn't affected - but it could happen...).
it's somehow the same idea as for v6, just for v4. for a lot of users it is not super useful, because they do not get multiple v4 addresses from...
iirc it masks the leftmost part.
reopening so we add something about this to the docs.