Cloudron App Packagers
That sounds like a classic timezone issue. Allday appointments don't really need timezone information, but lots of client still include them.
And when a client then parses it, that wants to use a different timezone you end up with an appointment that is shown over multiple days because it starts at e.g. 1:00 and not 0:00 because of the timezone.
Calendars are not as easy as they look.
I think X-Permitted-Cross-Domain-Policies is for the long dead adobe flash which used to use some crossdomain.xml . X-Content-Type-Options: nosniff might be worth putting back. But over time, I have removed many headers like X-Frame-Options (which is in OWASP) because they are causing browser warnings.
You can use this thread to track updates to the SeaweedFS package.
Please open issues in a separate topic instead of replying here.
This is fascinating! https://github.com/orgs/rustfs/discussions/2213 I wonder if we could simply swap it out in the dockerfile?
It would be nice if they could be hosted by the local registry app.
The docker images? That should already work and is close to my above suggestion with a private registry. You'd just need to configure the docker registry in the Cloudron dashboard under
/#/docker.
I believe what @robi meant is to be able to store the CloudronVersions.json in a registry, much like what authentik does with blueprints.
The convenience and the standardization benefits of using CloudronVersions.json and its features shouldn't be restricted to publicly accessible URLs.
Whether be it manually pasting a CloudronVersions.json's content in my dashboard, I'd like to be able to install my private custom applications this way.
@James thank you
I had not initially intended to use CloudronVersions in this way, but it is a real time saver.
Yep, once an app is published, probably no trimming (unless very old revoked versions).
