infra/nixos
5
0
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions

dma-monolith: update and cut the announcements feed off at Oct 1 #4

Open
sparky wants to merge 1 commit from monolith-publish-cutoff into main
pull from: monolith-publish-cutoff
merge into: infra:main
Conversation 0 Commits 1 Files changed 2 +10 -6
sparky commented 2026-10-27 03:09:10 -07:00
Member
Copy link

Deploys dma/monolith PR 43 and turns its cutoff on, so the announcements feed and the /announcements page only publish #news threads opened from October 1 onward.

What changes

  • flake.lock: bumps dma-monolith from c763fcf to 69849ae, that PR's merge commit. go.mod didn't change, so the vendor hash is the same.
  • host.nix: adds publishedSince = "2026-10-01T00:00:00-07:00"; to the announcements feed.

Both are in one commit on purpose. The old build rejects the unknown publishedSince key, and the new build refuses to start if the page's feed doesn't set it. Either half alone takes the whole site down on the next restart. To roll back, revert the commit as a whole.

This supersedes #3, the stopgap that hid the same threads by message ID. #3 can be closed once this merges.

After merge

Someone with SSH access to dreamflasher runs this once comin reports the deploy in #infra-log:

systemctl restart microvm@dma-monolith

Config changes don't restart the VM on their own yet. Until the restart, the VM keeps serving the old build with the old config, which is safe but still shows the pre-October threads.

Checking it

After the restart, https://dma.space/api/feeds/announcements.json and https://dma.space/announcements should list only threads opened on or after October 1. Three threads qualified on October 26, down from 18.

Not in this PR

The quotes feed gets a cutoff too, but every quote in it right now predates October 1, so the date is still an open question. It's a config-only change and can land separately.

Deploys [dma/monolith PR 43](https://codeberg.org/dma/monolith/pulls/43) and turns its cutoff on, so the announcements feed and the /announcements page only publish #news threads opened from October 1 onward. ## What changes - `flake.lock`: bumps `dma-monolith` from c763fcf to 69849ae, that PR's merge commit. `go.mod` didn't change, so the vendor hash is the same. - `host.nix`: adds `publishedSince = "2026-10-01T00:00:00-07:00";` to the announcements feed. Both are in one commit on purpose. The old build rejects the unknown `publishedSince` key, and the new build refuses to start if the page's feed doesn't set it. Either half alone takes the whole site down on the next restart. To roll back, revert the commit as a whole. This supersedes #3, the stopgap that hid the same threads by message ID. #3 can be closed once this merges. ## After merge Someone with SSH access to dreamflasher runs this once comin reports the deploy in #infra-log: ``` systemctl restart microvm@dma-monolith ``` Config changes don't restart the VM on their own yet. Until the restart, the VM keeps serving the old build with the old config, which is safe but still shows the pre-October threads. ## Checking it After the restart, https://dma.space/api/feeds/announcements.json and https://dma.space/announcements should list only threads opened on or after October 1. Three threads qualified on October 26, down from 18. ## Not in this PR The quotes feed gets a cutoff too, but every quote in it right now predates October 1, so the date is still an open question. It's a config-only change and can land separately.
dma-monolith: update and cut the announcements feed off at Oct 1
All checks were successful
CI / nixos (push) Successful in 7m44s
Details
CI / nixos (pull_request) Successful in 7m37s
Details
a2ced81a24 
Bumps dma-monolith to 69849ae (dma/monolith#43), which adds a per-feed
publishedSince cutoff, and sets it on the announcements feed so only
#news threads opened from 2026-10-01 onward are published.

The two changes have to land together: the old build rejects the
unknown publishedSince key, and the new build refuses to start when the
announcements page's feed doesn't set it. Revert them together too.

Config changes don't restart the VM on their own yet, so after comin
deploys this, run `systemctl restart microvm@dma-monolith` on
dreamflasher.
sparky requested review from diamond 2026-10-27 03:09:22 -07:00
All checks were successful
CI / nixos (push) Successful in 7m44s
Details
CI / nixos (pull_request) Successful in 7m37s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin monolith-publish-cutoff:monolith-publish-cutoff
git switch monolith-publish-cutoff

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff monolith-publish-cutoff
git switch monolith-publish-cutoff
git rebase main
git switch main
git merge --ff-only monolith-publish-cutoff
git switch monolith-publish-cutoff
git rebase main
git switch main
git merge --no-ff monolith-publish-cutoff
git switch main
git merge --squash monolith-publish-cutoff
git switch main
git merge --ff-only monolith-publish-cutoff
git switch main
git merge monolith-publish-cutoff
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
diamond
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/nixos!4
No description provided.