chore: publish 2.3.3+1.20.5-rootless release

chore: publish 2.3.2+1.20.3-rootless release
chore: publish 2.3.1+1.20.1-rootless release
2023-10-30 12:43:03 +00:00 · 2023-08-28 14:08:11 +02:00 · 2023-07-25 12:53:45 +01:00 · 2023-07-25 12:52:59 +01:00 · 2023-07-25 12:50:30 +01:00 · 2023-06-06 17:31:14 +02:00
7 changed files with 15 additions and 6 deletions
--- a/abra.sh
+++ b/abra.sh
@ -1,4 +1,4 @@
-export APP_INI_VERSION=v9
+export APP_INI_VERSION=v10
 export DOCKER_SETUP_SH_VERSION=v1

 abra_backup_app() {
--- a/app.ini.tmpl
+++ b/app.ini.tmpl
@ -71,3 +71,10 @@ ENABLED         = true
 FILE_EXTENSIONS = .rst
 RENDER_COMMAND  = rst2html
 IS_INPUT_FILE   = false
+
+[log]
+MODE=console
+LEVEL=WARN
+STACKTRACE_LEVEL=None
+ENABLE_ACCESS_LOG=false
+ENABLE_XORM_LOG=false
--- a/compose.forgejo.yml
+++ b/compose.forgejo.yml
@ -2,4 +2,4 @@ version: '3.8'

 services:
  app:
-    image: codeberg.org/forgejo/forgejo:1.18.2-0-rootless
+    image: codeberg.org/forgejo/forgejo:1.19.3-0-rootless
--- a/compose.mariadb.yml
+++ b/compose.mariadb.yml
@ -8,7 +8,7 @@ services:
      - GITEA_DB_NAME=gitea
      - GITEA_DB_USER=gitea
  db:
-    image: "mariadb:10.9"
+    image: "mariadb:10.11.2"
    command: |
      mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
--- a/compose.postgres.yml
+++ b/compose.postgres.yml
@ -8,7 +8,7 @@ services:
      - GITEA_DB_NAME=gitea
      - GITEA_DB_USER=gitea
  db:
-    image: postgres:9.6
+    image: postgres:15.4
    environment: 
      - POSTGRES_DB=gitea
      - POSTGRES_USER=gitea
--- a/compose.yml
+++ b/compose.yml
@ -3,7 +3,7 @@ version: "3.8"

 services:
  app:
-    image: "gitea/gitea:1.18.5-rootless"
+    image: "gitea/gitea:1.20.5-rootless"
    configs:
      - source: app_ini
        target: /etc/gitea/app.ini
@ -61,7 +61,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=2.1.0+1.18.5-rootless
+        - coop-cloud.${STACK_NAME}.version=2.3.3+1.20.5-rootless


 networks:
--- a/release/2.1.2+1.19.3-rootless
+++ b/release/2.1.2+1.19.3-rootless
@ -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
+
Author	SHA1	Message	Date
3wc	73970dd79c	chore: publish 2.3.3+1.20.5-rootless release	2023-10-30 12:43:03 +00:00
3wc	9153c4db2a	chore: publish 2.3.2+1.20.3-rootless release	2023-08-28 14:08:11 +02:00
3wc	b95eae3b57	chore: publish 2.3.1+1.20.1-rootless release	2023-07-25 12:53:45 +01:00
3wc	d18379a364	Bump APP_INI_VERSION	2023-07-25 12:52:59 +01:00
3wc	46bb242fe7	chore: publish 2.3.0+1.20.1-rootless release	2023-07-25 12:50:30 +01:00
Philipp Rothmann	f9249f1284	chore: publish 2.2.0+1.19.3-rootless release	2023-06-06 17:31:14 +02:00
Philipp Rothmann	9fe02cb19f	reduce logging verbosity	2023-06-06 16:19:52 +02:00
javielico	1e612d84a2	Merge pull request 'Updated images for MariaDB/Gitea and Postgres to latest stable or LTS' (#31 ) from javielico/gitea:master into master Reviewed-on: coop-cloud/gitea#31	2023-05-18 10:36:25 +00:00
Javielico	77dd223f94	Added commit message warning about Pgsql upgrade	2023-05-09 20:31:17 +01:00
Javielico	d5577a0f75	Mariadb to stable lts 10.11.2	2023-05-08 21:03:09 +01:00
Javielico	8f5587099d	Postgres up to 15.2	2023-05-08 21:01:16 +01:00
Javielico	d56a1474fe	Gitea up to latest stable 1.19.3	2023-05-08 20:58:58 +01:00
javielico	dc3f54d5ea	Merge pull request 'master' (#1 ) from coop-cloud/gitea:master into master Reviewed-on: #1	2023-05-08 19:47:16 +00:00
				`@ -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`