Installed a pinned release, configured admin-only lockout keyed by username and client IP, added a lockout page, and verified cool-off and reset behavior in tests. Compatibility had to be checked across majors before a Django 5-safe pin was clear, and several options were confirmed from installed package source rather than the install guide alone.
- What worked
- Admin-only lockout, the standalone authentication backend, the database handler, cool-off, and username/IP reset commands matched the need to protect staff login without challenging webhooks or authenticated writes.
- What got in the way
- The newest major on the index did not list support for the project's Django 5 line, so classifiers and source had to be compared to settle on 7.1.0. Proxy IP, middleware order, and admin-only behavior were not obvious from the installation page without reading package defaults.
