chore: publish 5.0.0+v6.0.0 release

README.md

@@ -7,8 +7,8 @@
 * **Status**: 2, beta
 * **Image**: [`listmonk/listmonk`](https://hub.docker.com/r/listmonk/listmonk/), 2, upstream
 * **Healthcheck**: No
-* **Backups**: Yes
-* **Email**: Yes
+* **Backups**: No
+* **Email**: ?
 * **Tests**: 2
 * **SSO**: No
 <!-- endmetadata -->
@@ -21,4 +21,3 @@
    to save secrets in `pass`)
 4. `abra app config YOURAPPDOMAIN` - be sure to change `$DOMAIN` to something that resolves to your Docker swarm box. Nothing to change apart from the DOMAIN at the moment.
 5. `abra app deploy YOURAPPDOMAIN`
-6. To make media uploads work, go to Settings->Media uploads and set upload path to "/uploads" and click the Save-button.

compose.yml

@@ -3,7 +3,7 @@ version: "3.8"
 
 services:
   app:
-    image: listmonk/listmonk:v6.1.0
+    image: listmonk/listmonk:v6.0.0
     networks:
       - internal
       - proxy
@@ -31,7 +31,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=9000"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - "coop-cloud.${STACK_NAME}.version=5.1.0+v6.1.0"
+        - "coop-cloud.${STACK_NAME}.version=5.0.0+v6.0.0"
     volumes:
       - "uploads:/uploads"
 

release/5.0.0+v6.0.0

@@ -1,17 +0,0 @@
-!!! Postgres major version upgrade and volume change !!!
-We're bumping from postgres 13 to 18 and the storage location of files has
-changed from /var/lib/postgres/data to /var/lib/postgres/18. Volume was
-adjusted accordingly. Take a dump of DB before the upgrade by running
-
-pg_dump -U listmonk -Fc -b -f /var/lib/postgres/data/dump
-
-in the db container of the app. Then pull this file out from the docker volume
-
-Then deploy the new version of the app. Next, copy the dump that you just
-made into new volume /var/lib/docker/volumes/your_app_name_postgres/_data/dump
-After that you can run
-
-pg_restore --clean -U listmonk -d listmonk /var/lib/postgres/dump
-
-Afterwards you should restart the db container and it should be all good.
-