Improve admin stats and restore Cloudflare visitor IPs #1000
No reviewers
Labels
No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
javascript
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MyVideoGameList/myvideogamelist.com!1000
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/admin-registration-improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Restyle admin game usage counts, highlight suspicious and banned users, and restore real visitor IPs behind Cloudflare.
Verification: 105 focused/regression tests pass; the full suite passes with 1,394 passed and 2 skipped (512 MB test-process memory limit). PHPStan, Pint, frontend build, and diff checks pass. The Cloudflare updater also successfully fetched 15 IPv4 and 7 IPv6 ranges from the live official endpoints during isolated testing.
Deployment: Enable the Laravel scheduler runner, perform an initial range refresh with the explicit deployment environment, and retain the writable range snapshot across releases. Setup commands are documented in README.md. No database migrations or dependency changes. Historical stored IPs and alerts are unchanged.
Related: #49 and #937.