Vikunja update to 0.24.1 (#1230)

Co-authored-by: Malte Kiefer <malte.kiefer@mailbox.org>
Co-authored-by: nmfretz <nmfretz@gmail.com>

vikunja/data/proxy/nginx.conf

@@ -1,12 +0,0 @@
-server {
-    listen 80;
-
-    location / {
-        proxy_pass http://frontend:80;
-    }
-
-    location ~* ^/(api|dav|\.well-known)/ {
-        proxy_pass http://api:3456;
-        client_max_body_size 20M;
-    }
-}

vikunja/docker-compose.yml

@@ -3,13 +3,13 @@ version: "3.7"
 services:
   app_proxy:
     environment:
-      APP_HOST: vikunja_proxy_1
-      APP_PORT: 80
+      APP_HOST: vikunja_web_1
+      APP_PORT: 3456
       # vikunja has its own auth, so we don't need to use transparent umbrel auth here
       PROXY_AUTH_ADD: "false"
 
   db:
-    image: mariadb:10.11.6@sha256:20a8bd91d972c97cffded88f2ba0ab533c8988b2dc08090c57d50caf7114ed20
+    image: mariadb:10.11.8@sha256:75f6e61397758489d1dccf95db33b6b49ebfc7ec1253d40060fdf8ceb7f938a3
     command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
     environment:
       MYSQL_ROOT_PASSWORD: supersecret
@@ -19,32 +19,23 @@ services:
     volumes:
       - ${APP_DATA_DIR}/data/db:/var/lib/mysql
     restart: on-failure
+    healthcheck:
+      test: ["CMD-SHELL", "mysqladmin ping -h localhost -u $$MYSQL_USER --password=$$MYSQL_PASSWORD"]
+      interval: 2s
+      start_period: 30s
 
-  api:
-    image: vikunja/api:0.22.1@sha256:c9415431e6235229302bb8f9ee6660b74c24859d1e8adbc4a3e25bd418604b57
+  web:
+    image: vikunja/vikunja:0.24.2@sha256:c31c7d6cad49038ab8a7d1414845d4c45539b43dd6ddd082bcd148e6fcd7b01c
     environment:
+      # VIKUNJA_SERVICE_PUBLICURL: <http://<the public ip or host where Vikunja is reachable>
       VIKUNJA_DATABASE_HOST: vikunja_db_1
       VIKUNJA_DATABASE_PASSWORD: secret
       VIKUNJA_DATABASE_TYPE: mysql
       VIKUNJA_DATABASE_USER: vikunja
       VIKUNJA_DATABASE_DATABASE: vikunja
       VIKUNJA_SERVICE_JWTSECRET: ${APP_SEED}
-      VIKUNJA_SERVICE_FRONTENDURL: http://${DEVICE_DOMAIN_NAME}/
     volumes: 
       - ${APP_DATA_DIR}/data/files:/app/vikunja/files
     depends_on:
       - db
     restart: on-failure
-
-  frontend:
-    image: vikunja/frontend:0.22.1@sha256:f0223d441997fe29c377d0b476dc4bb2fc091b44b9c24d76b1b88c213df520c5
-    restart: on-failure
-
-  proxy:
-    image: nginx:1.25.3@sha256:4c0fdaa8b6341bfdeca5f18f7837462c80cff90527ee35ef185571e1c327beac
-    volumes:
-      - ${APP_DATA_DIR}/data/proxy/nginx.conf:/etc/nginx/conf.d/default.conf:ro
-    depends_on:
-      - api
-      - frontend
-    restart: on-failure

vikunja/umbrel-app.yml

@@ -2,7 +2,7 @@ manifestVersion: 1
 id: vikunja
 category: files
 name: Vikunja
-version: "0.22.1"
+version: "0.24.2"
 tagline: The open-source, self-hostable to-do app
 description: >-
   Think of Vikunja like the notebook you have with all your things to keep track of. But with superpowers.
@@ -21,8 +21,25 @@ description: >-
   🛠️ Use It How You Need It
 
   You can view your tasks in the classic list view - or in a Gantt Chart, or Table view, or Kanban Board. Whatever you need!
-releaseNotes:
-  This is a patch release with many small bug fixes and improvements. Full release notes are available at https://vikunja.io/blog/2024/01/vikunja-frontend-and-api-v0.22.1-was-released/
+releaseNotes: >-
+  Welcome to Vikunja v0.24! There are many new features and improvements in this release. Some highlights include:
+    - New Views Functionality: The new views system allows you to customize how you see your tasks in each project.
+    - Improved Filters: You can now create more complex and precise filters using a simple query language.
+    - Emoji Reactions: You can now react to tasks and comments with emojis, similar to many modern communication platforms.
+    - Automatically create teams from openid claims: Automatically place users into the correct teams based on their roles or attributes in your organization's identity system, saving time on manual user management.
+    - New UI languages: The Vikunja web UI is now available in Portuguese Brazilian, Croatian, and Ukrainian.
+    - and much more!
+
+  🚨 Breaking changes:
+
+  
+  Due to the way the views were changed, we had to do a few breaking changes:
+    - Kanban buckets now belong to a project view instead of directly to a project.
+    - New endpoint to change a task's position in a view. The position now depends on the context (the view) of the task. As a result, the position and kanban_position task attributes are no longer available.
+    - New endpoint to move a task between buckets. Passing a bucket_id when updating the task will not have an effect anymore, you'll need to use the new dedicated endpoint for that.
+    - If you shared a project via a link share and specified a view with the link, you'll need to update the link to point to the view.
+  
+  Full release notes are available at https://vikunja.io/changelog/whats-new-in-vikunja-0.24.0
 developer: Vikunja
 website: https://vikunja.io/
 dependencies: []