Repository navigation
0.10.0
·
270 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Added
- Install without cloning (#33). Each release attaches
dinnerbell-X.Y.Z.tar.gzand its SHA-256:compose.yamlpinned to the release,compose.secrets.yaml,.env.example, both Slack manifests,deploy/dinnerbell-testwith its compose files, andINSTALL.md. CI builds it from the tag and attests it, sogh attestation verifycovers it like the image. docs/install.md installs from it in eight steps. dinnerbell initwrites a new env file. It asks for the hostname, admin email, time zone, household name, and the Slack app's values, with a hint for each; generatesDINNERBELL_SECRET_KEY; and checks the result asdinnerbell config checkdoes. Secrets are read without echo and never printed. It writes to--output FILEwith mode 600, or to standard output when that isn't a terminal.init --testwrites a test instance's file and refuses production's secrets, client ID, and hostname from.env.
Changed
- Documentation only: step 9 of the setup guide again explains that
DINNERBELL_BASE_URLmust match the public URL, whatDINNERBELL_ADMIN_EMAILdoes, thatDINNERBELL_HOUSEHOLD_NAMEandDINNERBELL_TIMEZONEapply on first start only, and which secret keys Dinnerbell refuses. 0.9.1's rewrite had dropped these notes. - Badges climb three ladders (#130). Frequent (1, 10, 50, 100, 200) keeps the meal badges; Occasional (1, 5, 20, 50, 100) is for Bright Idea and Good Host; Rare (1, 3, 10, 25, 50) is for On a Roll, Scout, and Explorer, so every Diamond is within reach. Stats and App Home show each badge's next step on its own ladder.
- On a Roll has a grace week. A run survives one missed week, which doesn't count toward it; two missed weeks in a row still end it.
- Admin > Badges edits the three ladders, five counts each, validated as before, with Reset to defaults. Each save and reset is audited. The
badge_thresholdssetting holds one list per ladder; a single list from an earlier version is read as the Frequent ladder. - Tiers that the new ladders or the grace week put in reach are awarded quietly, as when an admin lowers a threshold, so the channel gets no burst of posts.
- Documentation only: the README opens with what Dinnerbell needs (a container host, a Slack workspace, and an HTTPS hostname), a diagram of how the pieces connect, and how a dinner works in five steps (#34).
Upgrade notes
- Badges: on the first start, members may receive badge tiers quietly: the new ladders and On a Roll's grace week put them in reach. Nothing is posted to Slack for them, and no earned tier is removed. A custom ladder you saved earlier becomes the Frequent ladder. No database revision ships for this.
- Install bundle: optional. An install from a git clone keeps working, and upgrades the same way. To move to the bundle, see docs/install.md; keep the directory name
dinnerbellso compose finds the same data volume, and copy.env(and.env.test,secrets/,secrets-test/if you use them) into it.
Image
ghcr.io/dsmorgan/dinnerbell:0.10.0@sha256:977e7807f9cd7bb79ed966522dafbd6402c866831f2e65aab290467369fe6e80
Install bundle
dinnerbell-0.10.0.tar.gz and its .sha256 are attached and attested. See docs/install.md.