feat: add Waxum template - #1074
Conversation
dosubot
Bot
added
size:S
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59568d5c38
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - 3451 | ||
| environment: | ||
| - SUPERADMIN_TOKEN=${SUPERADMIN_TOKEN} | ||
| - WHATSAPP_STORAGE_PATH=/app/whatsapp_sessions |
There was a problem hiding this comment.
When this template runs without DATABASE_URL/SQLITE_PATH, Waxum defaults its embedded SQLite database to ./waxum.db under /app, while this compose file only mounts /app/whatsapp_sessions. On a Dokploy redeploy or container recreation, the session files survive but the database-backed state such as sessions metadata, webhooks, message history, scheduled/blast jobs, and console state is lost; set the SQLite path inside the mounted volume or add a volume for the DB as well.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Good catch on the underlying concern, though the premise is slightly off: waxum's SQLite default doesn't resolve to /app/waxum.db — it joins WHATSAPP_STORAGE_PATH (source: src/db/mod.rs), which this template already points at the mounted volume, so it was already persisted. Made it explicit anyway in 88d3fa4 with SQLITE_PATH=/app/whatsapp_sessions/waxum.db so it's no longer implicit/undocumented behavior.
Waxum's default SQLite path already resolves inside WHATSAPP_STORAGE_PATH, so this was already persisted, but make it explicit so it doesn't depend on undocumented default derivation surviving a redeploy. Addresses: Dokploy#1074 (review)
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Tested this end-to-end on a live Dokploy instance — everything checks out. ✅ Legitimacy
Template conventions
Deploy test (real instance)
LGTM — ready to merge. |
2 participants
Summary
Adds Waxum — a WhatsApp REST API gateway written in Rust — as a new Dokploy template.
waxum_datavolume alongside WhatsApp session state).SUPERADMIN_TOKEN, generated with the${password:32}helper.fdciabdul/waxum:0.11.5(pinned, matches the current GitHub release).Test plan
node build-scripts/generate-meta.js --checkpasses (511 templates validated, including this one).fdciabdul/waxum:0.11.5exists on Docker Hub.SUPERADMIN_TOKEN/PORTenv var names and the SQLite default (noDATABASE_URLrequired) directly against the waxum source.