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.

The vxrail leaves the k3s cluster: the forge's data comes out of local-path, the agent is stopped and uninstalled

1 of 8 done 7 open · 1 merged in 7 days · moved 45m ago

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

on pace for 2027-01-01

Read the issue #11825

Limbs

The forge moves from its pod to the systemd unit on the vxrail, on the same data directory 6 open · 1 merged in 7 days · moved 45m ago 1 of 7 done

Blocked

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

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

1 closed

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