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

dma-monolith: hide announcements from before 2026-10-01 #3

Open
sparky wants to merge 1 commit from announcements-cutoff-stopgap into main
pull from: announcements-cutoff-stopgap
merge into: infra:main
Conversation 0 Commits 1 Files changed 1 +20
sparky commented 2026-10-26 16:33:33 -07:00
Member
Copy link

The announcements feed (JSON and Atom) publishes every #news thread back to December 2025. Only the /announcements page has a date cutoff, and it starts at August 15. Members posting in #news before now didn't know their posts would go on the website, so this hides the 15 threads opened before 2026-10-01.

It uses the existing excludeMessageIds option. Excluding a thread's opening message drops the whole entry from the JSON feed, the Atom feed, and the page. Three threads stay public: the October 3 electrolysis night, "signal bridge at long last", and "HVAC Reminder".

This is a stopgap. A monolith PR adds a per-feed publish cutoff to the config. Once that's deployed, this list gets replaced by a single date.

After merge

Config-only changes don't restart the monolith VM yet (the restartUnits issue), so someone with SSH access has to run systemctl restart microvm@dma-monolith on dreamflasher after the deploy finishes. Then https://dma.space/api/feeds/announcements.json should list 3 items.

The announcements feed (JSON and Atom) publishes every #news thread back to December 2025. Only the /announcements page has a date cutoff, and it starts at August 15. Members posting in #news before now didn't know their posts would go on the website, so this hides the 15 threads opened before 2026-10-01. It uses the existing `excludeMessageIds` option. Excluding a thread's opening message drops the whole entry from the JSON feed, the Atom feed, and the page. Three threads stay public: the October 3 electrolysis night, "signal bridge at long last", and "HVAC Reminder". This is a stopgap. A monolith PR adds a per-feed publish cutoff to the config. Once that's deployed, this list gets replaced by a single date. ## After merge Config-only changes don't restart the monolith VM yet (the `restartUnits` issue), so someone with SSH access has to run `systemctl restart microvm@dma-monolith` on dreamflasher after the deploy finishes. Then https://dma.space/api/feeds/announcements.json should list 3 items.
dma-monolith: hide announcements from before 2026-10-01
All checks were successful
CI / nixos (push) Successful in 7m25s
Details
CI / nixos (pull_request) Successful in 7m18s
Details
b40b1ce013 
The announcements feed publishes every #news thread back to December
2025, from before members knew #news posts would appear on the
website. Exclude the 15 threads opened before 2026-10-01 until the
monolith has a per-feed publish cutoff.
All checks were successful
CI / nixos (push) Successful in 7m25s
Details
CI / nixos (pull_request) Successful in 7m18s
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 announcements-cutoff-stopgap:announcements-cutoff-stopgap
git switch announcements-cutoff-stopgap

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff announcements-cutoff-stopgap
git switch announcements-cutoff-stopgap
git rebase main
git switch main
git merge --ff-only announcements-cutoff-stopgap
git switch announcements-cutoff-stopgap
git rebase main
git switch main
git merge --no-ff announcements-cutoff-stopgap
git switch main
git merge --squash announcements-cutoff-stopgap
git switch main
git merge --ff-only announcements-cutoff-stopgap
git switch main
git merge announcements-cutoff-stopgap
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
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!3
No description provided.