I agree, such situations where upstream leaves us with no good path to migrate existing instances are pretty bad. We usually spend much time on finding ways to migrate, as it is indeed part of what we see as value we provide. In this case however @girish was next to me for quite some time trying to find a way, but after explaining the introduced mismatch of table foreign key constraint ids, it simply wasn't possible.
Depending on the case, we sometimes create a new appstore id for the app package to avoid existing installations to break on update, but it also means there won't be any more updates and users are still stuck 😕
@nj I tried installing it to my cloudron and it built successfully, but I ran into an issue with the cloudron cli during installation saying that I need to specify a subdomain (when I clearly did specify a subdomain), then I ran out of time to mess with it until later this week.
This is something I need as well, working on rolling out PaperlessNGX to replace an existing storage system and need to be able to store office documents as well so that all documents related to an entity are together.
It looks like Tika and Gotenberg both have docker containers available.
Do we need to have separate Tika and Gotenberg apps like we have OnlyOffice and Collabra Online as a separate apps though they are not usable on their own and are used by NextCloud for handling office documents?
right now the URL field in my sqlite table does not point to anything because in the original context of this database, the path to the domain is defined in the config.yaml file but exactly like for the LAMP container, I'm wondering how I can just say to nocodb the media files are at /media/
I think I understand what you are saying. You want https://nocodb.osintukraine.com/media/date/3.MP4 to somehow work. So, this won't work currently because it's not possible to override paths of nocodb like we do in the LAMP app. In the LAMP app, since the app is something we control, it's fine to configure paths the way we want. Doing the same for nocodb is going to cause problems at some point. For example, what it nocodb starts serving things in /media from next release. Or maybe it uses that path already for some internal use, who knows.
So, instead, what do you think of either a) linking these to the LAMP app itself or b) setup a separate LAMP app instance under static.osintukraine.com and make it serve images from there. Nocodb can simple reference this for "static" contents. Would some idea like that work?
Update Prometheus to 2.38.0
Web: Add a /api/v1/format_query HTTP API endpoint that allows pretty-formatting PromQL expressions. #11036 #10544 #11005
UI: Add support for formatting PromQL expressions in the UI. #11039
DNS SD: Support MX records for discovering targets. #10099
Templates: Add toTime() template function that allows converting sample timestamps to Go time.Time values. #10993
PromQL: When a query panics, also log the query itself alongside the panic message. #10995
Update metabase to 0.44.1
Fix incorrect hash for Advanced fieldvalues (#24740)
Confusing UX after performing password reset (#24700)
Changing existing filters in Simple GUI will replace other existing filters (#24664)
Cannot set caching duration to less than a second (#24657)
Correct spelling of pulse setting notification-retry-randomizaion-factor (#24653)
Update Synapse to 1.65.0
Add support for stable prefixes for MSC2285 (private read receipts). (#13273)
Add new unstable error codes ORG.MATRIX.MSC3848.ALREADY_JOINED, ORG.MATRIX.MSC3848.NOT_JOINED, and ORG.MATRIX.MSC3848.INSUFFICIENT_POWER described in MSC3848. (#13343)
Use stable prefixes for MSC3827. (#13370)
Add a new module API method to translate a room alias into a room ID. (#13428)
Add a new module API method to create a room. (#13429)
Also, the reason for nextcloud update is that it has some slightly tricky optimization to change ownership of files carefully. It also changes the default data directory of newer nextcloud installations.
Just kidding! You don't need any of that crap. Just drag and drop a folder, or select a file. That's literally it. Now you can host a website from your laptop or your phone or your smartwatch or your toaster.