Repository navigation
Move deployment to PriveeDeploy; Privee runs CI only - #174
Merged
Merged
Conversation
Self-hosters deploy the prebuilt image with the MaxDac/PriveeDeploy template instead of forking and editing fly.toml. The upstream fly.toml and deploy are unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f7f40cc8-cd7f-4b72-9d7b-30ce408b2b9f
Privee no longer deploys or publishes images: remove main.yml and fly.toml, run CI on pushes to main, and revert the Dockerfile build arg. Point the README and self-hosting docs at PriveeDeploy, and add a deploy-privee skill so agents can trigger a deploy with gh. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f7f40cc8-cd7f-4b72-9d7b-30ce408b2b9f
MaxDac
changed the title
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Privee now holds the code and its checks only; deployment lives in MaxDac/PriveeDeploy.
main.yml(deploy job) andfly.toml; the bauta settings move to PriveeDeploy'sfly.toml.ci.ymlalso runs on pushes tomain(it was previously called frommain.yml).docs/self-hosting.md: configuration reference, AGPL obligations, notes for other platforms (Docker/K8s, unsupported).deploy-priveeskill (.github/skills/deploy-privee/SKILL.md) and an AGENTS.md pointer: agents check CI, confirm with the user, thengh workflow run deploy.yml -R MaxDac/PriveeDeploy -f ref=<sha>.GET /api/app/info.Companion PR: MaxDac/PriveeDeploy#1.
Before deploying: add the
FLY_API_TOKENsecret to PriveeDeploy (fly tokens create deploy -a bauta). The oldproductionenvironment and secret on Privee can be deleted.