PocketGit turns your PocketCorp into a full git forge of your own.
Not a mirror, not a backup folder: the real thing. Repositories, issues, pull requests with review, releases, wikis, organisations and teams, a web interface you open from any device, and CI that runs GitHub-style workflows. It is Forgejo — the open-source forge behind Codeberg — installed, configured and secured for you.
SET UP IN A FEW MINUTES, WITHOUT A TERMINAL
One press downloads and starts the forge, with a live log so you can see it happen. Then you pick the username and password you will sign in with, and that is the whole setup. No config files, no installer page, no ports to open.
PRIVATE FROM THE FIRST SECOND
Most self-hosted forges start life as an open signup page on the public internet, and whoever finds the URL first becomes the admin. Yours never is: registration is off before the forge has ever answered a request, and your account is created directly, from inside. Repositories are private by default.
WHAT YOU GET
- A real address with a real certificate — https://pocketgit-sync.<your server>.apps.pocketcorp.agency, wired and renewed by PocketCorp. Clone and push over HTTPS from anywhere
- Unlimited repositories, unlimited collaborators, unlimited private code. No seat count, no per-user price, no repository limit — it is your server
- Issues, pull requests, code review, releases, wikis, labels, milestones
- Forgejo Actions: CI workflows in the GitHub Actions format
- Your agent can use it: ask it to "put this in git" or "back up my workspace" and it creates the repository and pushes, with its own scoped token — never your password
- A dashboard on your server page: status, repositories, one-press updates to the newest Forgejo, and the exact commands to push into any repository
- Your code stays yours. It lives in ~/git on your own machine, and uninstalling PocketGit leaves every repository exactly where it is
Runs in Docker, which every PocketCorp already has, and needs about 300 MB of memory — comfortable on the base plan. Git over HTTPS with an access token (the dashboard hands you one); SSH remotes are not used, so there is no extra port to open. During installation, approve the sudo prompts from your dashboard when asked — or enable auto-approval in the top right of the dashboard first, then it is completely hands-free.