The Phorge API: authenticated users and API keys manage tenants, images, instances, memberships and API keys.
It creates phorge.fr objects on the control cluster; Crossplane turns them into Incus and OpenFGA objects.
make vet lint test build
OIDC_ISSUER=... OIDC_AUDIENCE=... OPENFGA_URL=... OPENFGA_API_KEY=... OPENFGA_STORE_ID=... ./bin/phorge-apiThe configuration is read from the environment; the process refuses to start and lists everything wrong if a required value is missing. See Configuration.
Pages are in docs/, grouped by what you want to do: how-to guides, reference, explanation.
The kinds the API manages and the platform behind them are documented in phorge-fr/Hangar: Phorge API kinds.
Every change starts from an issue and goes through a pull request; the rules (issue link, label, milestone, assignee, reviewer) are in the organization's GOVERNANCE and CONTRIBUTING. Planned work is on the public Roadmap. Everyone taking part follows the Code of Conduct.
Report vulnerabilities privately, as described in the security policy. Do not open a public issue for them.
Licensed under the Apache License 2.0.