Compare commits

..

1 Commits

Author SHA1 Message Date
a00d8abe08 chore(deps): update postgres docker tag to v15.15 2025-11-20 18:45:41 +00:00
6 changed files with 9 additions and 56 deletions

View File

@ -1,6 +1,6 @@
TYPE=forgejo
TYPE=gitea
DOMAIN=forgejo.example.com
DOMAIN=gitea.example.com
LETS_ENCRYPT_ENV=production
COMPOSE_FILE="compose.yml"
ENABLE_BACKUPS=true
@ -8,12 +8,11 @@ COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
# COMPOSE_FILE="$COMPOSE_FILE:compose.sqlite3.yml"
# COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml"
SECRET_LFS_JWT_SECRET_VERSION=v1 # length=43
# Enable to use forgejo instead of gitea
# COMPOSE_FILE="$COMPOSE_FILE:compose.forgejo.yml"
# SECRET_LFS_JWT_SECRET_VERSION=v1 # length=43
# Anubis
# COMPOSE_FILE="$COMPOSE_FILE:compose.anubis.yml"
GITEA_DOMAIN="${DOMAIN}"
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

@ -1,32 +0,0 @@
# Forgejo Recipe Maintenance
All contributions should be made via a pull request. This is to ensure a
certain quality and consistency, that others can rely on.
## Maintainer Responsibilities
A recipe maintainer has the following responsibilities:
- Respond to pull requests / issues within a week
- Make image security updates within a day
- Make image patch / minor updates within a week
- Make image major updates within a month
In order to fullfill these responsibilities a recipe maintainer:
- Has to watch the repository (to get notifications)
- Needs to make sure renovate is configured properly
## Pull Requests
A pull request can be merged if it is approved by at least one maintainer. For
pull requests opened by a maintainer they need to be approved by another
maintainer. Even though it is okay to merge a pull request with one approval, it
is always better if all maintainers looked at the pull request and approved it.
## Become a maintainer
Everyone can apply to be a recipe maintainer:
1. Watch the repository to always get updates
2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
3. Once the pull request gets merged you will be added to the [forgejo maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/forgejo-maintainers).

View File

@ -3,7 +3,6 @@
[![Build Status](https://build.coopcloud.tech/api/badges/coop-cloud/forgejo/status.svg)](https://build.coopcloud.tech/coop-cloud/forgejo)
<!-- metadata -->
* **Maintainer**: [@p4u1](https://git.coopcloud.tech/p4u1), [@fauno](https://git.coopcloud.tech/fauno)
* **Category**: Development
* **Status**: 5
* **Image**: [`forgejo/forgejo`](https://codeberg.org/forgejo/-/packages/container/forgejo/13-rootless), 4, upstream
@ -60,9 +59,3 @@ ssh -T -p 2222 git@my.gitea.example.com
```
Note that gitea should be configured to listen to port 2222, i.e. `GITEA_SSH_PORT=2222` in the gitea config.
## Protect Forgejo from scrapers with Anubis
Uncomment the Anubis compose file from the `.env` file and re-deploy the
app. Don't forget to actually [enable Anubis on the Traefik app
too](https://recipes.coopcloud.tech/traefik)!

View File

@ -1,7 +0,0 @@
---
version: "3.8"
services:
app:
deploy:
labels:
- "traefik.http.routers.${STACK_NAME}.middlewares=anubis,${STACK_NAME}_cors"

View File

@ -10,7 +10,7 @@ services:
secrets:
- db_password
db:
image: postgres:15.13
image: postgres:15.15
deploy:
labels:
backupbot.backup.pre-hook: "/pg_backup.sh backup"

View File

@ -3,7 +3,7 @@ version: "3.8"
services:
app:
image: codeberg.org/forgejo/forgejo:13.0.4-rootless
image: codeberg.org/forgejo/forgejo:13.0.2-rootless
configs:
- source: app_ini
target: /etc/gitea/app.ini
@ -89,7 +89,7 @@ services:
- "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"
- coop-cloud.${STACK_NAME}.version=5.0.3+13.0.4-rootless
- coop-cloud.${STACK_NAME}.version=5.0.0+13.0.2-rootless
networks: