64761ffe59
- the container running the job is to use leading it not being able to access the gitea instance when trying to push new docker image to registry
This is stack definition for Gite server running as Docker container.
Specs
- HTTPS publishing
- published via Traefik at "gitea.budakova.org"
- uses TLS provided by Let's Encrypt
- uses
/home/knee-cola/docker/d-gitea/as root in which directories mounted for Gitea image reside
Why TLS
TLS is used to that docker registry, which is a part of Gitea can be served over HTTPS using LAN IP address.
Installation
- create directories on docker host machine
cd /home/knee-cola/docker/
mkdir -p ./d-gitea
mkdir -p ./d-gitea/data
mkdir -p ./d-gitea/config
sudo chown 1000:1000 ./d-gitea/config/ ./d-gitea/data/
- Deploy stack/service
Use Portainer to deploy docker-compose.yaml
This container doesn't use any env variables.
- Publish the Gitea web console
At Cloudflare under ZeroTrust configure tunnel connecting the machine to CloudFlare: add a new published website gitea.budakova.org pointing to https://10.10.1.200
- Publish Gitea registry
At CloudFlare create a new A DNS record registry.budakova.org pointing to local IP address 10.10.1.200.
- Access the UI console
Complete the setup in web console at https://gitea.budakova.org