Vikunja update to 0.24.1

[MalteKiefer]

No description provided.

[nmfretz]

Thanks very much for all the app updates and submissions @MalteKiefer! Very much appreciated. We will take a look at these shortly. Please ignore the random close/open from me testing a workflow.

[MalteKiefer]

External port is need, there is a mobile app for Vikunja.

[nmfretz]

Thanks again for this Vikunja update @MalteKiefer. Looks like the Vikunja developers are simplifying the architecture for Docker Compose deployments which is nice.

I've left some comments below with suggested changes. In addition to those changes, we can also delete the entire proxy subdirectory within vikunja/data since the new compose architecture no longer requires nginx.

Once addressed, we can test to make sure the app is working well for fresh installs and app updates.

[nmfretz]

With the change to a single image for the frontend and api, it looks like VIKUNJA_SERVICE_FRONTENDURL is no longer needed. Although we could add in VIKUNJA_SERVICE_PUBLICURL for good measure:
https://vikunja.io/changelog/whats-new-in-vikunja-0.23.0#using-docker

[nmfretz]

This is actually a huge update for users on umbrelOS since they will be updating from 0.22.1 to 0.24.1.
We could summarize some of the major relevant changes here or just mention that it is a major update from 0.22.1 to 0.24.1. That way users don't think they are just updating to a patch.

[nmfretz]

External port is need, there is a mobile app for Vikunja.

We shouldn't need to expose a separate port on the host for this to work. Right now the app_proxy is making Vikunja available on port 4523 on the host, with the proxy's auth disabled. So as-is, a user would connect a client to Vikunja with something like http://umbrel.local:4523/... (I'm guessing on the connection format). To make it easier for users, we could change the main port for the app to 3456 in the umbrel-app.yml so that our port would match documentation or forum posts that users may search for online when troubleshooting. So this way users would connect via http://umbrel.local:3456/....

Are you currently running the alpha pre-release mobile app? If so, do you know what url is usually used to connect, and would you be able to help test that it works?

[github-actions]

🎉   Linting finished with no errors or warnings   🎉

Thank you for your submission! This is an automated linter that checks for common issues in pull requests to the Umbrel App Store.

Please review the linting results below and make any necessary changes to your submission.

Linting Results

Severity	File	Description
ℹ️	vikunja/docker-compose.yml	Potentially using unsafe user in service "db": The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.
ℹ️	vikunja/docker-compose.yml	Potentially using unsafe user in service "web": The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.

Legend

Symbol	Description
❌	Error: This must be resolved before this PR can be merged.
⚠️	Warning: This is highly encouraged to be resolved, but is not strictly mandatory.
ℹ️	Info: This is just for your information.

[nmfretz]

I have gone ahead and made the required changes and tested Vikunja as a fresh install and update from v0.22.1 with data persistence. Thanks again for this PR!