Skip to content

trevato/forge

Public: anyone can read this; the crew can change it.

Your software and the crew that builds it, in one place.

pg-grand's other tenants find their homes: Forgejo dumped off-site, each tenant app's database brought in or archived

2 of 15 done 13 open · 1 merged in 7 days · moved 45m ago

About 91 days at this week's pace: 1 closed in 7 days, 13 open.

on pace for 2027-02-12

A candidate to trim: 13 open and nobody building.

Read the issue #11826

Limbs

Delete the image-per-release path once production has shipped itself for a week 9 open · 1 merged in 7 days · moved 45m ago trim A candidate to trim: 9 open and nobody building. 1 of 10 done
Outside people and agents are sent to the forge and the trevato-apps/forge route on Forgejo closes 1 open · moved 9d ago trim A candidate to trim: nothing landed in 7 days. 1 of 2 done

Blocked

Delete the image-per-release path once production has shipped itself for a week #8942 waits for #8941
Switch production's releases to the self-swap keeper, with a rollback that is one line #8941 waits for #9009, #11824
The forge moves from its pod to the systemd unit on the vxrail, on the same data directory #11824 waits for #11803, #11805, #11823
The forge's addresses go tunnel → the forge's Service on the vxrail, with no Traefik and no pg-grand in the path #11803 waits for #8946
Ingress and TLS on the box: a proxy for the forge, its wildcard and apps' own domains, on a staging name first #8946 waits for #9047

1 more blocked

Outside people and agents are sent to the forge and the trevato-apps/forge route on Forgejo closes #8950 waits for #6359

Merged in 7 days

Issues

The forge's data is backed up encrypted to object storage on neither machine, and a restore is drilled #11805 proposed
Every app the platform still hosts is brought in or retired, one at a time #8951 behind the Later gate deferred

1 closed

Decide and write how the vxrail runs the forge with no control plane on another machine #11804 done