jhalitaksoy/mancala
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add publishing mancala.js to the TODO

Browse Source 
The apps use the engine from the repo, so publishing the fixed engine to
npm is left as the last deployment step.
This commit is contained in:
Halit Aksoy 2026-10-16 10:52:15 +03:00
parent e81e0e0841
commit 5b0cddf416
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TODO.md
View File

@ -74,6 +74,8 @@ See `docs/specs/web-redesign`.
- [ ] Back up the Postgres volume (Keycloak and saved games), e.g. a daily `pg_dumpall` - [ ] Back up the Postgres volume (Keycloak and saved games), e.g. a daily `pg_dumpall`
- [ ] Set `MANCALA_DB_PASSWORD` and `POSTGRES_PASSWORD` in `apps/.env` on the server; the `postgres` volume replaces - [ ] Set `MANCALA_DB_PASSWORD` and `POSTGRES_PASSWORD` in `apps/.env` on the server; the `postgres` volume replaces
`keycloak-db`, so Keycloak starts with a fresh database there `keycloak-db`, so Keycloak starts with a fresh database there
- [ ] Last step: publish a new `mancala.js` to npm (it is at `0.0.2-beta.3` from 2022), so the published engine skips
the opponent's store when sowing. The apps do not need it; they use `packages/mancala.js` through `link:`
## Security ## Security