m038/intotheeast-com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix all internal cross-references after restructure

Browse Source
This commit is contained in:
Mischa
2026-06-21 12:48:04 +02:00
parent 93aa6d9b42
commit 65597de00d
29 changed files with 4738 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/production-todo.md
+36 -31
View File
@@ -1,35 +1,44 @@
# Production Todo
Fresh server — no Grav installed yet. Work through these sections in order.
Work through Phase 1 first (local fixes and config), then Phase 2 (server deployment and go-live).
---
## 1. Pre-install: fix server-install.sh for Grav 2.0
## Phase 1 — Local fixes before deploy
`server-install.sh` has a gap: it copies the `grav-admin` bundle (which includes `user/plugins/admin2/`) but then immediately does `rm -rf user && git clone ...`, which wipes admin2. It never gets reinstalled because GPM doesn't carry Admin2.
These are changes made in the local dev environment and committed before anything touches the server.
- [ ] Update `server-install.sh` to stash admin2 before wiping user/, then restore it after:
### 1.1 Fix server-install.sh for Grav 2.0
```bash
# After "cp -rf grav-admin/. ." and before "rm -rf user":
cp -rf grav-admin/user/plugins/admin2 /tmp/admin2-plugin
`server-install.sh` had a gap: it copied the `grav-admin` bundle (which includes `user/plugins/admin2/`) but then immediately did `rm -rf user && git clone ...`, wiping admin2. It never got reinstalled because GPM doesn't carry Admin2.
# After "git clone $USER_REPO user" and "mkdir -p user/plugins ...":
cp -rf /tmp/admin2-plugin user/plugins/admin2
rm -rf /tmp/admin2-plugin
```
- [x] Updated `server-install.sh` to stash admin2 before wiping user/, then restore it after
- [x] Removed `admin` from `plugins.txt` — Admin2 replaces it and both conflict on `/admin`
- [ ] Remove `admin` from `plugins.txt` if it's there — Admin2 replaces it and both conflict on `/admin`
### 1.2 Update config for production
## 2. Pre-install: configure .env
- [x] Cleared `custom_base_url` in `user/config/system.yaml` (was pointing to local dev IP; empty means Grav auto-detects from the request, which works both locally and in production)
### 1.3 Content and metadata
- [ ] Set `date_start` on the Japan & Korea 2026 trip page (`user/pages/01.trips/japan-korea-2026/trip.md`)
- [ ] Add `cover_image` to the trip page (used on the trips listing)
- [ ] Upload actual GPX route file(s) to `/gpx-manager` or drop directly into `user/pages/01.trips/japan-korea-2026/`
- [ ] Run `make content-push` to push all local changes to Gitea
---
## Phase 2 — Server deployment and go-live
### 2.1 Configure .env
- [ ] Set `GRAV_VERSION=2.0.0-rc.9` in `.env`
- [ ] Set `GRAV_CHANNEL_SUFFIX=?testing` in `.env` (makes the download URL resolve to the RC)
- [ ] Set `GRAV_CHANNEL_SUFFIX=?testing` (makes the download URL resolve to the RC)
- [ ] Set `REMOTE_HOST`, `REMOTE_USER`, `REMOTE_PORT`, `REMOTE_HOME` for the production server
- [ ] Set `USER_REPO` and `MAIN_REPO` (Gitea URLs)
- [ ] Set `GITEA_HOST`, `GITEA_USER`, `GITEA_TOKEN` for the install-time clone
## 3. Run the install
### 2.2 Run the install
```bash
make remote-env-setup # writes Gitea token to server temporarily
@@ -39,32 +48,28 @@ make remote-env-remove # removes token from server
After install, the script prints the server's SSH public key. Add it as a deploy key to both Gitea repos so `make remote-fetch` works going forward.
## 4. Post-install: config
### 2.3 Verify post-install config
These are already committed to the `user/` repo so they'll be present after the clone — just verify:
These are committed to the `user/` repo and should be present after the clone — just confirm:
- [ ] `user/config/system.yaml` has `accounts.type: flex` and `pages.type: flex`
- [ ] `user/config/system.yaml` `custom_base_url` is set to the production domain (currently set to the local dev IP — update before deploy)
- [ ] `user/accounts/mischa.yaml` has `api.super: true` and `api.access: true`
- [ ] Disable old admin plugin: set `enabled: false` in `user/plugins/admin/admin.yaml` on production (or ensure it's not in `plugins.txt`)
- [ ] Old admin plugin is absent from `plugins.txt` (not installed)
## 5. Post-install: switch to production mode
### 2.4 Switch to production mode
- [ ] Set `twig.cache: true` in `user/config/system.yaml`
- [ ] Smoke test: submit one post via `/post`, confirm entry appears in `/trips/japan-korea-2026/dailies` immediately (verifies cache-on-save plugin works with Twig cache on)
- [ ] Set `twig.cache: true` in `user/config/system.yaml` on the server (do not commit this to the repo — it would break local dev)
- [ ] If Grav can't auto-detect the base URL (e.g. behind a reverse proxy), set `custom_base_url` in `user/config/system.yaml` on the server
## 6. Security
### 2.5 Smoke test
- [ ] Submit one post via `/post`, confirm entry appears in `/trips/japan-korea-2026/dailies` immediately (verifies cache-on-save plugin works with `twig.cache: true`)
### 2.6 Security
- [ ] Change admin password to a strong production password
- [ ] Confirm `/post` requires login — unauthenticated visitors must not be able to post
## 7. Map tiles
### 2.7 Map tiles
- [ ] Register at [carto.com](https://carto.com) and review terms for production traffic (CartoDB dark tiles are free but registration is expected for production use)
## 8. Content
- [ ] Set `date_start` on the Japan & Korea 2026 trip page (`user/pages/01.trips/japan-korea-2026/trip.md`)
- [ ] Upload actual GPX route file(s) to the trip page media — currently no GPX files, so the map shows no route
- [ ] Add `cover_image` to the trip page (used on the trips listing)
- [ ] Run `make content-push` to push any local content changes to Gitea before going live