# authentik | Gitea | Leantime CI/CD stack

A portainer docker compose stack for Raspberry Pi with authentik, Gitea and Leantime for local CI/CD (you are accessing it right now)

I am trying to use my vpnstack NPM portainer docker compose setup to use https for this, but failing miserably...

So far I got it working in my LAN, but https won't work.... tried but it always times out... I suspect it's the nginx it uses I had similar problems with snipeit on proxmox, but there I managed to fix it at the end, although local access was not possible anymore if I did...

steps taken:
in NPM settings, added 

proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
client_max_body_size 512M;

in the portainer editor, added

      - GITEA__server__ROOT_URL=https://${GITEA_DOMAIN}
      - GITEA__server__DOMAIN=${GITEA_DOMAIN}
      - GITEA__server__SSH_DOMAIN=${GITEA_DOMAIN}
      - GITEA__server__SSH_PORT=2022
      - GITEA__server__HTTP_PORT=3000
      - GITEA__server__PROTOCOL=http
      - GITEA__server__HTTP_ADDR=0.0.0.0
      - GITEA__server__LOCAL_ROOT_URL=http://localhost:3000/

where ${GITEA_DOMAIN} in the portainer env is set to my duckdns: JavITYourWay.duckdns.org

tried also with     

    extra_hosts:
      - hostname:192.x.x.x

but saw no difference...

so now cat /data/gitea/conf/app.ini at least I know can be edited easily with - GITEA__server__XXXXX and it maps to ${XXXXX}

[server]
APP_DATA_PATH = /data/gitea
DOMAIN = XXXXX
SSH_DOMAIN = XXXXX
HTTP_PORT = XXXXX
ROOT_URL = http://XXXXX:3000
DISABLE_SSH = false
SSH_PORT = XXXXX
SSH_LISTEN_PORT = 22
LFS_START_SERVER = true
LFS_JWT_SECRET = XXXXX
PROTOCOL = XXXXX
HTTP_ADDR = 0.0.0.0
LOCAL_ROOT_URL = http://XXXXX:3000/

results: when forcing SSL in NPM timeout, so I had to not force it and revert back everything...


TO-DO: 
 - learn nginx properly to at least show Gitea via https to the world (right now only http works)
 - make authentik also NPM so I can use it outside my LAN (strech GOAL)