Compare commits

..

4 Commits

Author SHA1 Message Date
621c483397 fix(#54): remove unused env GITEA_DOMAIN 2026-05-29 00:17:26 -07:00
6aa52c1e73 fix abra command in documentation
Some checks failed
continuous-integration/drone/push Build is failing
2026-05-19 03:43:34 +00:00
3wc
db92e97071 docs: Fix broken README links, appease markdown linter 2026-01-08 21:29:48 -05:00
d86d742ed1 Adds missing access controll headers
All checks were successful
continuous-integration/drone/push Build is passing
2025-10-27 18:29:54 +01:00
5 changed files with 23 additions and 10 deletions

View File

@ -12,7 +12,6 @@ COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
# COMPOSE_FILE="$COMPOSE_FILE:compose.forgejo.yml"
# SECRET_LFS_JWT_SECRET_VERSION=v1 # length=43
GITEA_DOMAIN=git.example.com
GITEA_ALLOW_ONLY_EXTERNAL_REGISTRATION=true
GITEA_APP_NAME="Git with solidaritea"
GITEA_AUTO_WATCH_NEW_REPOS=false

View File

@ -15,7 +15,7 @@
## Basic usage
1. Set up Docker Swarm and [`abra`][abra]
1. [Set up Docker Swarm and `abra`][operators-tutorial]
2. Deploy [`coop-cloud/traefik`][cc-traefik]
3. `abra app new gitea --secrets` (optionally with `--pass` if you'd like
to save secrets in `pass`)
@ -23,12 +23,15 @@
your Docker swarm box
5. `abra app deploy YOURAPPDOMAIN`
[operators-tutorial]: https://docs.coopcloud.tech/operators/tutorial/
[cc-traefik]: https://git.coopcloud.tech/coop-cloud/traefik/
## Create first user
Run
```bash
abra app run YOURAPPNAME app gitea -c /etc/gitea/app.ini admin user create --username USERNAME --admin --random-password --email EMAIL
abra app run YOURAPPNAME app -- gitea -c /etc/gitea/app.ini admin user create --username USERNAME --admin --random-password --email EMAIL
```
See the [Gitea command-line documentation](https://docs.gitea.io/en-us/command-line/) for more options. Make sure not to forget the `-c /etc/gitea/app.ini`.
@ -36,25 +39,34 @@ See the [Gitea command-line documentation](https://docs.gitea.io/en-us/command-l
## Enable SSH
You most certainly want to be able to access your repository over SSH. To do so, make sure you uncomment the right lines in the configuration for `traefik`.
```
```sh
abra app config YOURTRAEFIKAPP
```
There uncomment or add these lines:
```
```sh
GITEA_SSH_ENABLED=1
COMPOSE_FILE="compose.yml:compose.gitea.yml"
```
Then redeploy traefik:
```
```sh
abra app undeploy YOURTRAEFIKAPP
abra app deploy YOURTRAEFIKAPP
```
You might need to wait a bit. To check if it worked, you can run
```
```sh
telnet my.gitea.example.com 2222
```
Once you have added a public SSH key, you can check that you can connect to your gitea server with
```
```sh
ssh -T -p 2222 git@my.gitea.example.com
```

View File

@ -1,4 +1,4 @@
export APP_INI_VERSION=v22
export APP_INI_VERSION=v21
export DOCKER_SETUP_SH_VERSION=v1
export PG_BACKUP_VERSION=v1

View File

@ -87,7 +87,7 @@ SMTP_ADDR = {{ env "GITEA_MAILER_ADDR" }}
SMTP_PORT = {{ env "GITEA_MAILER_PORT" }}
USER = {{ env "GITEA_MAILER_USER" }}
PASSWD = {{ secret "smtp_password" }}
PROTOCOL = smtp
MAILER_TYPE = smtp
{{ end }}
{{ if eq (env "GITEA_OAUTH2_CLIENT_ENABLED") "1" }}
@ -109,3 +109,4 @@ IS_INPUT_FILE = false
MODE=console
LEVEL=WARN
STACKTRACE_LEVEL=None
ENABLE_XORM_LOG=false

View File

@ -84,6 +84,7 @@ services:
- "traefik.tcp.services.${STACK_NAME}-ssh.loadbalancer.server.port=${GITEA_SSH_PORT}"
- "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}_cors"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolallowmethods=GET,OPTIONS,PUT"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolallowheaders=content-type,authorization"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"