Docs

FAQ

What you need to run powder, how the single-tenant model works, the licence and where to get help.

What do I need?

One Linux box with Docker for powder itself, one or more servers to deploy to (they can be the same box), a GitHub repository per app, a GitHub OAuth app for sign-in, and a domain with DNS you control. See Self-hosting.

Is there a hosted version or an account with you?

No. Powder is single-tenant. You install it on your own servers, your data stays there, and there is no account with us. The first GitHub login on an empty install becomes the admin. Other users get a 403 single_tenant; there is no setting to allow them.

Which licence?

AGPL-3.0. The licence text is in the repository.

Does powder need a registry or a CI service?

No. It builds the image on your server on every push. Rollback uses the previous images kept on that server.

What happens if a build or a check fails?

The old container keeps serving. See How a deploy runs.

Are backups restored automatically?

No. Restore is manual. See Backups.

Releases

Releases are tagged vX.Y.Z on GitHub, with notes in CHANGELOG.md. To upgrade, run git pull (the public history is linear) or git fetch --tags && git checkout vX.Y.Z, then bin/self-deploy.sh. See Upgrading.

How do I get help?

Email [email protected], or open an issue on GitHub.