Jake Howard

Making it print the current state of the router would be simple enough, but what does it provide? If the user starts their project **then** the router, the list is...

Correct, There's 1 crab router, which handles routing traffic from the given port to the specific project. A process is routable if it's got a `$VIRTUAL_HOST` and has been allocated...

It looks like there's a `LOG_USER_ATTRIBUTE` setting to change what attribute is logged. Perhaps if this is explicitly set to `False` or `None`, logging of the user attribute is skipped....

From what you mentioned above, the `AnonymousUser` check will still touch the session, as `request.user` needs to be populated from the session, which involves reading from it. As for the...

This is interesting, and highlights a bit of a feature hole in the current implementation. We currently don't bust the cache when a page is updated :facepalm: That deals with...

Having a different namespace for loading could make sense, at least to keep the implementations separate and stop `wagtailcore_tags` swelling. I think the tags need to keep the `wagtail` prefix,...

Backup is a bit more complex, especially trying to do it in an automated way like this. For example, if some databases exist in the container but not others, it's...

My suggestions for fixing: 1. Add opt-out functionality for validating the strength of the passwords used to protect pages, using Django's existing [password validators](https://docs.djangoproject.com/en/stable/topics/auth/passwords/#integrating-validation). This helps protect users from using...

> The feature isn't very secure Why? It follows Wagtail's existing permissions model for pages (which ought to be secure), collects and compares passwords in a secure way, and correctly...

Reviving this old issue a little, because I think it'd make redirect _so much_ easier to work with. This could be something we add as part of the import process,...