WIP: State save - pre-deploy Wiki.js manual steps documented
This commit is contained in:
@@ -148,3 +148,26 @@ You're inheriting a live community. Real subscribers are coming. The infrastruct
|
||||
Take good care of them. 🔥❄️
|
||||
|
||||
— The Ignition, Chronicler #91
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ PRE-DEPLOY MANUAL STEP — Subscriber Wiki Auth (Task #138)
|
||||
|
||||
**BEFORE Code deploys REQ-2026-04-15-subscriber-wiki-auth:**
|
||||
|
||||
Michael must do these steps in the Wiki.js admin panel at `subscribers.firefrostgaming.com`:
|
||||
|
||||
1. **Create 6 user groups** (in this order):
|
||||
- Awakened
|
||||
- Elemental
|
||||
- Knight
|
||||
- Master
|
||||
- Legend
|
||||
- Sovereign
|
||||
|
||||
2. **Note the group IDs** — Wiki.js assigns numeric IDs. Pass these to Code so the tier→group mapping is correct.
|
||||
|
||||
3. **Generate an API key** — Wiki.js Admin → API Access → Generate key. Add to Arbiter `.env` as `WIKIJS_API_KEY`.
|
||||
|
||||
**Do NOT deploy until these three steps are complete.** Code needs the group IDs to finish the implementation.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user