Compare commits

...

22 Commits

Author SHA1 Message Date
6643761eff fix backup label 2024-04-30 15:15:49 +02:00
2fe008de5a update forgejo to 1.20.1-0-rootless 2024-04-29 16:12:15 +02:00
3915bf7493 add backup label 2024-04-29 15:03:49 +02:00
3wc
46bb242fe7 chore: publish 2.3.0+1.20.1-rootless release
All checks were successful
continuous-integration/drone/push Build is passing
2023-07-25 12:50:30 +01:00
f9249f1284 chore: publish 2.2.0+1.19.3-rootless release
All checks were successful
continuous-integration/drone/push Build is passing
2023-06-06 17:31:14 +02:00
9fe02cb19f reduce logging verbosity 2023-06-06 16:19:52 +02:00
1e612d84a2 Merge pull request 'Updated images for MariaDB/Gitea and Postgres to latest stable or LTS' (#31) from javielico/gitea:master into master
All checks were successful
continuous-integration/drone/tag Build is passing
Reviewed-on: #31
2023-05-18 10:36:25 +00:00
77dd223f94 Added commit message warning about Pgsql upgrade 2023-05-09 20:31:17 +01:00
d5577a0f75 Mariadb to stable lts 10.11.2 2023-05-08 21:03:09 +01:00
8f5587099d Postgres up to 15.2 2023-05-08 21:01:16 +01:00
d56a1474fe Gitea up to latest stable 1.19.3 2023-05-08 20:58:58 +01:00
dc3f54d5ea Merge pull request 'master' (#1) from coop-cloud/gitea:master into master
Reviewed-on: javielico/gitea#1
2023-05-08 19:47:16 +00:00
8b466acf66 chore: publish 2.1.0+1.18.5-rootless release 2023-03-15 13:18:39 -07:00
3wc
9cf26a0154 Switch to thecoopcloud/stack-ssh-deploy 2023-01-20 23:31:14 -08:00
3wc
a04fe41c1b Specify mariadb for tests 2023-01-20 22:38:13 -08:00
3wc
63118ecbd8 Fix CI by adding networks: [mass update] 2023-01-20 22:32:13 -08:00
3wc
cd0fff667a Automatically generate catalogue on release [mass update]
Re: coop-cloud/recipes-catalogue-json#4
2023-01-20 22:32:13 -08:00
9413c79e8f chore: publish 2.0.1+1.18.2-rootless release 2023-01-20 11:00:24 +01:00
7d7761dec6 feat: add forgejo overwrite
Some checks failed
continuous-integration/drone/push Build is failing
2023-01-20 10:55:04 +01:00
936fb940cb Revert "fix: drop db_password from main compose def"
This reverts commit 89400089ec.

db_password secret is still needed in app service to set the db
secret in app.ini.tmpl
2023-01-20 10:50:35 +01:00
3wc
e2cd36873c Update abra syntax in examples (finally) [mass update] 2023-01-19 16:27:03 -08:00
89400089ec fix: drop db_password from main compose def
Now available in mariadb/postgresql compose files.
2023-01-17 10:45:19 +01:00
9 changed files with 51 additions and 12 deletions

View File

@ -3,14 +3,17 @@ kind: pipeline
name: deploy to swarm-test.autonomic.zone name: deploy to swarm-test.autonomic.zone
steps: steps:
- name: deployment - name: deployment
image: decentral1se/stack-ssh-deploy:latest image: thecoopcloud/stack-ssh-deploy:latest
settings: settings:
host: swarm-test.autonomic.zone host: swarm-test.autonomic.zone
stack: gitea stack: gitea
networks:
- proxy
generate_secrets: true generate_secrets: true
purge: true purge: true
deploy_key: deploy_key:
from_secret: drone_ssh_swarm_test from_secret: drone_ssh_swarm_test
compose: "compose.yml:compose.mariadb.yml"
environment: environment:
APP_INI_VERSION: v1 APP_INI_VERSION: v1
DOCKER_SETUP_SH_VERSION: v1 DOCKER_SETUP_SH_VERSION: v1
@ -37,11 +40,17 @@ trigger:
- master - master
--- ---
kind: pipeline kind: pipeline
name: recipe release name: generate recipe catalogue
steps: steps:
- name: release a new version - name: release a new version
image: thecoopcloud/drone-abra:latest image: plugins/downstream
settings: settings:
command: recipe gitea release server: https://build.coopcloud.tech
deploy_key: token:
from_secret: abra_bot_deploy_key from_secret: drone_abra-bot_token
fork: true
repositories:
- coop-cloud/auto-recipes-catalogue-json
trigger:
event: tag

View File

@ -6,6 +6,9 @@ COMPOSE_FILE="compose.yml"
COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml" COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
# COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml" # COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml"
# Enable to use forgejo instead of gitea
# COMPOSE_FILE="$COMPOSE_FILE:compose.forgejo.yml"
GITEA_DOMAIN=git.example.com GITEA_DOMAIN=git.example.com
GITEA_ALLOW_ONLY_EXTERNAL_REGISTRATION=true GITEA_ALLOW_ONLY_EXTERNAL_REGISTRATION=true
GITEA_APP_NAME="Git with solidaritea" GITEA_APP_NAME="Git with solidaritea"

View File

@ -19,9 +19,9 @@
2. Deploy [`coop-cloud/traefik`][cc-traefik] 2. Deploy [`coop-cloud/traefik`][cc-traefik]
3. `abra app new gitea --secrets` (optionally with `--pass` if you'd like 3. `abra app new gitea --secrets` (optionally with `--pass` if you'd like
to save secrets in `pass`) to save secrets in `pass`)
4. `abra app YOURAPPDOMAIN config` - be sure to change `$DOMAIN` to something that resolves to 4. `abra app config YOURAPPDOMAIN` - be sure to change `$DOMAIN` to something that resolves to
your Docker swarm box your Docker swarm box
5. `abra app YOURAPPDOMAIN deploy` 5. `abra app deploy YOURAPPDOMAIN`
## Create first user ## Create first user

View File

@ -71,3 +71,10 @@ ENABLED = true
FILE_EXTENSIONS = .rst FILE_EXTENSIONS = .rst
RENDER_COMMAND = rst2html RENDER_COMMAND = rst2html
IS_INPUT_FILE = false IS_INPUT_FILE = false
[log]
MODE=console
LEVEL=WARN
STACKTRACE_LEVEL=None
ENABLE_ACCESS_LOG=false
ENABLE_XORM_LOG=false

5
compose.forgejo.yml Normal file
View File

@ -0,0 +1,5 @@
version: '3.8'
services:
app:
image: codeberg.org/forgejo/forgejo:1.20.1-0-rootless

View File

@ -8,7 +8,13 @@ services:
- GITEA_DB_NAME=gitea - GITEA_DB_NAME=gitea
- GITEA_DB_USER=gitea - GITEA_DB_USER=gitea
db: db:
image: "mariadb:10.9" image: "mariadb:10.11.2"
deploy:
labels:
backupbot.backup: "true"
backupbot.backup.pre-hook: 'mysqldump --single-transaction -u root -p"$$(cat /run/secrets/db_root_password)" gitea > /var/lib/mysql/backup.sql'
backupbot.backup.post-hook: "rm -rf /var/lib/mysql/backup.sql"
backupbot.backup.path: "/var/lib/mysql/backup.sql"
command: | command: |
mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
environment: environment:

View File

@ -8,7 +8,13 @@ services:
- GITEA_DB_NAME=gitea - GITEA_DB_NAME=gitea
- GITEA_DB_USER=gitea - GITEA_DB_USER=gitea
db: db:
image: postgres:9.6 image: postgres:15.3
deploy:
labels:
backupbot.backup: "true"
backupbot.backup.pre-hook: "PGPASSWORD=$$(cat $${POSTGRES_PASSWORD_FILE}) pg_dump -U $${POSTGRES_USER} $${POSTGRES_DB} > /var/lib/postgresql/data/backup.sql"
backupbot.backup.post-hook: "rm -r /var/lib/postgresql/data/backup.sql"
backupbot.backup.path: "/var/lib/postgresql/data"
environment: environment:
- POSTGRES_DB=gitea - POSTGRES_DB=gitea
- POSTGRES_USER=gitea - POSTGRES_USER=gitea

View File

@ -3,7 +3,7 @@ version: "3.8"
services: services:
app: app:
image: "gitea/gitea:1.18.0-rootless" image: "gitea/gitea:1.20.1-rootless"
configs: configs:
- source: app_ini - source: app_ini
target: /etc/gitea/app.ini target: /etc/gitea/app.ini
@ -48,6 +48,7 @@ services:
failure_action: rollback failure_action: rollback
order: start-first order: start-first
labels: labels:
- "backupbot.backup=true"
- "traefik.enable=true" - "traefik.enable=true"
- "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`)" - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`)"
- "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure" - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
@ -61,7 +62,7 @@ services:
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}" - "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.accesscontrolmaxage=100"
- "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true" - "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"
- coop-cloud.${STACK_NAME}.version=2.0.0+1.18.0-rootless - coop-cloud.${STACK_NAME}.version=2.3.0+1.20.1-rootless
networks: networks:

View File

@ -0,0 +1,2 @@
Beware that you'll also be updating Postgres if you're running it. Usually with major updates it might involve pg_dumpall / pg_restore either side of the upgrade because the server app doesn't know how to upgrade data storage formats, won't launch if it detects an old data format, a pg_upgrade command is available. More info on https://git.coopcloud.tech/coop-cloud/gitea/pulls/31