Repository navigation
Replies: 2 comments 5 replies
|
are you committing over http(s) or ssh? is it running directly on the host or inside of the docker container? what the error message looks like on the git side? |
1 reply
|
I just tried the simplest gitea setup I can imagine, this is my compose version: "3" services:
gitea:
image: gitea/gitea:1.14.2
container_name: gitea
environment:
- USER_UID=1001
- USER_GID=1001
restart: always
volumes:
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000"
- "2222:22"
labels:
reproxy.port: '3000'
reproxy.route: '^/(.*)'
reproxy.dest: '/$$1'
reproxy:
image: umputun/reproxy:master
container_name: reproxy
hostname: reproxy
ports:
- "80:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- TZ=America/Chicago
- LISTEN=0.0.0.0:8080
- DOCKER_ENABLED=true
- DEBUG=trueworked just fine: |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Gitea version 1.14.3 built with GNU Make 4.1, go1.16.5 : bindata, sqlite, sqlite_unlock_notify
reproxy v0.8.0-4-g4fce9c4-master-20210620-20:43:04
settings /etc/reproxy
`git.mydomain.com:
I can't see commits in Gitea if it work through reproxy(502 returns), but i can if get comit directly. Can someone confirm this bug or i have a problem with settings?
All reactions