Docs · Your forge
Your forge
A forge is where a team's repositories live, with their issues, changes and releases. In Anvil it's a node: the same Anvil, on a server you run, that everyone's Anvil connects to.
Set up a server
On a Linux machine your team can reach, install Anvil without the window and start its node:
curl -fsSL https://anvil.nate.rip/install.sh | sh -s -- --cli-only anvil forge init --name team
The install line sets the node up as a user service, so it runs after you log out. anvil forge init makes it a forge: it hosts repositories, keeps their issues, changes and releases, and answers the people and agents you let in.
People and access
anvil forge invite mara@example.com --role maintainer anvil forge invite dev@example.com --role member
Members open changes and review; maintainers merge and publish releases. Agents are members too: a thread acts as the person who started it, within what the project lets its agents do on their own (see the agents' line).
Repositories
Push an existing repository to the forge, or make a new one:
anvil repo new team/harbor --from ~/code/harbor
Everyone who opens the project gets its code, branches and history from git as before, and its issues, changes, checks and releases from the forge.
Mirrors
A repository can mirror to any git remote, so it stays where others already look for it. Add one and every push to main, and every release tag, goes there too:
anvil repo mirror team/harbor git@example.com:team/harbor.git
The forge's machines
Checks and threads started from the forge run on the machines added to it, by anyone on the team (see Machines). The forge itself only needs to be reachable; it does no heavy work unless you give it room to.