Files
Portainer/README.md
T
2026-11-04 16:58:24 +01:00

1.2 KiB

portainer

Portainer CE stack, ready to deploy directly or through the gittea push-to-deploy CI.

Run it directly

docker compose up -d

Open https://localhost:9443 and create the admin user on first run (first visit wins — nobody can register afterwards).

Test it through Gitea (gittea CI)

  1. Create an empty repo in Gitea (e.g. portainer, main branch).
  2. If not done yet, add the webhook to the repo:
    • URL: http://deployer:9000/deploy
    • Secret: WEBHOOK_SECRET from the gittea .env
    • Trigger: push events
  3. Push this folder:
git remote add origin http://<gitea-host>:<port>/<user>/portainer.git
git push -u origin main
  1. The deployer clones the repo and runs docker compose up -d on every push that touches non-doc files. Watch it: docker logs -f gittea-deployer.

Notes

  • Only the compose file is needed; no deploy.sh in the repo means the deployer uses plain docker compose.
  • Port 9443 is configurable: PORTAINER_HTTPS_PORT=9444 docker compose up -d.
  • Port 9000 is intentionally not published (deployer default port).
  • Portainer manages the same Docker daemon the deployer uses — both mount docker.sock (root-equivalent access).