run the gitea sidecar in the mac light profile

The sidecar fronts a REMOTE instance — its URL and token live in
service_connections, set from /gitea — so it needs nothing installed on the
laptop. That is what separates it from the sidecars left out of this profile,
which supervise a local daemon or container.

It also had to be classified either way: defineProfile throws at load on a name
that is in neither include nor exclude, so leaving it unlisted broke the profile
outright rather than merely omitting it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-08 00:39:18 +01:00
co-authored by Claude Opus 5
parent d56be0301d
commit 2490392e57
+5
View File
@@ -32,6 +32,11 @@ module.exports = defineProfile({
// The terminal. Runs under node rather than bun — node-pty binds a native addon built against // The terminal. Runs under node rather than bun — node-pty binds a native addon built against
// node's ABI. That detail lives in ecosystem.config.cjs, not here. // node's ABI. That detail lives in ecosystem.config.cjs, not here.
'officer-pty', 'officer-pty',
// Included even though a laptop hosts no Gitea: this sidecar fronts a REMOTE instance. The URL and
// its token live in `service_connections`, set from /gitea, so it points at gitea.pastilhas.dev
// over the network and needs nothing installed here. That is what separates it from the sidecars
// below that supervise a local daemon or container.
'officer-gitea',
], ],
excluded: { excluded: {