The first project in this list
Purpose:
Verify that the application correctly handles traffic when deployed behind a reverse proxy (e.g., Nginx), including protocol forwarding, headers, redirects, and asset loading.
✅ Steps to Validate
Access via Proxy URL
Purpose:
Verify that the Approved Revs extension is installed and functioning correctly, ensuring content approval workflows are enforced before public display.
Steps to Validate
View a Page as Anonymous User
Validate user login flow and confirm access control restrictions are preserved after migration.
Ensure application connects to the MariaDB container reliably and consistently post-migration.
Ensure that file uploads (images, PDFs, attachments) work correctly after migration.
Uploads succeed without errors. Files are correctly stored and accessible.
Verify that all pages render correctly with consistent styles after migration.
1. Visit the Main Page and several subpages.
2. Check layout, fonts, spacing, and theming.
3. View in multiple browsers (Firefox, Chrome).
Stylesheets load correctly. No visual glitches, missing assets, or layout issues.
This test plan outlines the key areas to verify post-migration.
- Page rendering and CSS
- Database connectivity
- User login and permissions
- Uploads and file handling
- Verify workflow of the Approved Revs Extension
- Reverse proxy behavior
We can start out with this framework and keep track of project wins, and losses. This documentation format is being adopted rather late. Hopefully we still have time to fill in some of the gaps.
This project covers the migration of our legacy MediaWiki system to the new containerized infrastructure.
All test plans, feature outlines, and known issues will be documented as Project Docs.
This wiki is so old it's going to take three steps to update!