- clone repo
- insert .env and define
x_TOKENIDwhereMODE=X
# example .env
MODE=DEV
DEV_TOKENID="..."maketo build image & setup bound data
# docker image
make up
# or with local changes
make dev- the bot will check for updates on-startup and via webhook POSTs (if you set that up)
# add this to your .env to auto-update non breaking changes
REDEPLOY=1
# manually...
make update
make up # to restart# using
make up # start
make down # stop
# updates
make # for fresh clones
make update # this pulls first
# debug
make logs # follow output live
make dev # uses go run instead of docker, MODE=DEVThe frontend compiles to a static SPA embedded into the Go binary, so a
deployment is still one artifact and one process. Go serves both the pages and
the API on SERVER_PORT.
make web # compile the SPA into root/api/web/dist (go:embed reads it)
make dev # then run; skip `make web` and you get a "not built" notice pageReleases build the frontend in CI, so the published binary already contains it.