Identity carries the forge web address (forgeUrl), defaulted to https on the forge host #44

New issue

Closed

opened 2026-10-09 06:06:46 +01:00 by vnprc-agent · 2 comments

vnprc-agent commented

2026-10-09 06:06:46 +01:00

Identity carries the forge's web address, so a dev VM's forge CLI can be pointed at a plain-http forge on the private network instead of assuming https:// on the forge host.

Primary goals:

One field, forgeUrl — identity.forgeUrl is the base URL the forge CLI and any API client use, https://forge.anarch.diy in the template; the ssh host and port stay what they are, because clone transport and API transport differ.
Exported where the dev builder reads — lib.devIdentities.<vm>.forgeUrl carries it, beside forgeHost and forgePort, so allod/archetypes can render it into the VM.
Absent means today's behaviour — a fork whose identity predates the field evaluates unchanged: the export defaults to https://${forgeHost}, so no deployment has to edit its identity to take this.
A check proves both branches — a fixture identity without the field yields the default; one with it yields the value verbatim.

Current state and specifics

flake.nix builds devIdentities from identity.username forgeHost forgePort and the per-VM record; nothing names a URL. The forge CLI in allod/tools reads FORGE_URL and otherwise defaults to https://forge.anarch.diy, which is right for the template's forge and wrong for a forge VM serving plain http on a private address (the forge machine the templates now carry: allod/profiles hosts/service/forge, tls = false, Caddy on port 80 at the guest's address). The README's lib.devIdentities row lists the fields; it gains this one.

Scope

In: the identity field in the template identity.nix, the defaulted export in flake.nix, the README row, and the check. Out: rendering the value into a VM, which is allod/archetypes (the dev builder exports FORGE_URL); and the install script's second run that writes the forge VM's address into a fork, which is allod/deploy.

Part of allod/strategy#65

Identity carries the forge's web address, so a dev VM's forge CLI can be pointed at a plain-http forge on the private network instead of assuming `https://` on the forge host. Primary goals: - **One field, `forgeUrl`** — `identity.forgeUrl` is the base URL the `forge` CLI and any API client use, `https://forge.anarch.diy` in the template; the ssh host and port stay what they are, because clone transport and API transport differ. - **Exported where the dev builder reads** — `lib.devIdentities.<vm>.forgeUrl` carries it, beside `forgeHost` and `forgePort`, so `allod/archetypes` can render it into the VM. - **Absent means today's behaviour** — a fork whose identity predates the field evaluates unchanged: the export defaults to `https://${forgeHost}`, so no deployment has to edit its identity to take this. - **A check proves both branches** — a fixture identity without the field yields the default; one with it yields the value verbatim. ### Current state and specifics `flake.nix` builds `devIdentities` from `identity.username forgeHost forgePort` and the per-VM record; nothing names a URL. The `forge` CLI in `allod/tools` reads `FORGE_URL` and otherwise defaults to `https://forge.anarch.diy`, which is right for the template's forge and wrong for a forge VM serving plain http on a private address (the `forge` machine the templates now carry: `allod/profiles` `hosts/service/forge`, `tls = false`, Caddy on port 80 at the guest's address). The README's `lib.devIdentities` row lists the fields; it gains this one. ### Scope In: the identity field in the template `identity.nix`, the defaulted export in `flake.nix`, the README row, and the check. Out: rendering the value into a VM, which is `allod/archetypes` (the dev builder exports `FORGE_URL`); and the install script's second run that writes the forge VM's address into a fork, which is `allod/deploy`. Part of allod/strategy#65

vnprc-agent referenced this issue from allod/archetypes

2026-10-09 06:06:47 +01:00

Dev VMs render FORGE_URL from identity #142

vnprc-agent referenced this issue from allod/deploy

2026-10-09 06:06:47 +01:00

getting-started.sh --forge: point the dev VM at the forge VM #11

vnprc referenced this issue from a commit

2026-10-09 06:35:09 +01:00

identity: add forgeUrl, defaulted from forgeHost

vnprc-agent referenced this issue from allod/strategy

2026-10-09 13:03:32 +01:00

A Forgejo VM on the hypervisor: PRs and issues for a forge-less deployment #65

allod-agent added the

landed?

label

2026-10-21 22:27:19 +01:00

allod-agent commented

2026-10-21 22:37:16 +01:00

Member

Landed on master by direct commit 24f69b3 ("identity: add forgeUrl, defaulted from forgeHost"); closing on the owner's instruction.

Landed on master by direct commit 24f69b3 ("identity: add forgeUrl, defaulted from forgeHost"); closing on the owner's instruction.

allod-agent closed this issue

2026-10-21 22:37:16 +01:00

allod-agent commented

2026-10-21 23:32:36 +01:00

Member

Landed on master in commit 24f69b3: forgeUrl in identity.nix, exported with a default and checked in checks/forge-url.nix. Verified against the files on master today; closing as completed.

Landed on master in commit 24f69b3: forgeUrl in identity.nix, exported with a default and checked in checks/forge-url.nix. Verified against the files on master today; closing as completed.

allod-agent removed the

landed?

label

2026-10-21 23:32:36 +01:00