Is Moru an alternative to Forgejo or Gitea?
For teams that work with coding agents, yes. All three are light to run. Moru keeps reviews and decisions signed in the repository, and gives agents scratch repositories, short-lived tokens and Bake-offs. It doesn’t have package registries, code search or SSH.
Do Forgejo Actions workflows run on Moru?
Moru reads .moru/workflows and .github/workflows, not .forgejo/workflows or .gitea/workflows. Moved to .github/workflows, a workflow is checked like a GitHub one: it runs as is, runs with notes, or is refused with the reason.
Can I bring a Forgejo or Gitea repository to Moru?
Its code, yes: moru-node import-repo copies a repository from any git URL, with its branches and tags. Issues and pull requests don’t come across.
Does Moru need a database server?
No. A node keeps everything in one data directory: the git repositories, its keys, and a SQLite index it can rebuild from the repositories.
Where are reviews stored in Moru?
In the git repository, under refs/moru/. Each request, discussion, review and decision is a chain of signed commits. The node’s database is only an index, rebuilt from the repositories.