Ente
-
@andreasdueren said in Ente:
@robi Yes, I think this is not far from running. Don't have time to work on it today unfortunately
time to circle back?
@robi no pressure, huh 🥸
-
@robi no pressure, huh 🥸
@andreasdueren Hehe. just a gentle reminder of a previous completion attempt
-
Would love to see it soon in the Cloudron App Store!
-
Would love to see it soon in the Cloudron App Store!
@Nerdrelaxo same:)
Mobile App lot of faster than Immich, E2EE -
@Nerdrelaxo same:)
Mobile App lot of faster than Immich, E2EE@sponch Yes me too, but I've been struggling with this packaging but also I'm a bit discouraged because I've packaged two apps now but I'm not sure if they'll make it to the app store at all. I udnerstand maintaining apps brings additional overhead but trying to get packages working is an investment I'm not sure I want to make if I don't know if it will actually make it to the store.
-
@sponch Yes me too, but I've been struggling with this packaging but also I'm a bit discouraged because I've packaged two apps now but I'm not sure if they'll make it to the app store at all. I udnerstand maintaining apps brings additional overhead but trying to get packages working is an investment I'm not sure I want to make if I don't know if it will actually make it to the store.
@andreasdueren this is a continuing issue, the need for easy deployment for custom apps via the App Store, if necessary as unsupported apps.
Big picture view : however hard they try, and even with a bigger team, [@]staff will never be able to keep up with the flow of new software and demand from users for X or Y or very niche Z.
But there are many users who need an AppStore UI/process to install custom apps., rather than manual build and install.
We already have "unstable" as a status.
It would help greatly if there was also "unsupported", requiring only a basic initial review and no ongoing official support or maintenance.
AppDev and less techie users could be more free to explore/extend without creating a burden for Cloudron ops. -
@andreasdueren this is a continuing issue, the need for easy deployment for custom apps via the App Store, if necessary as unsupported apps.
Big picture view : however hard they try, and even with a bigger team, [@]staff will never be able to keep up with the flow of new software and demand from users for X or Y or very niche Z.
But there are many users who need an AppStore UI/process to install custom apps., rather than manual build and install.
We already have "unstable" as a status.
It would help greatly if there was also "unsupported", requiring only a basic initial review and no ongoing official support or maintenance.
AppDev and less techie users could be more free to explore/extend without creating a burden for Cloudron ops.@timconsidine … but then you get very close to Yunohost and the like that have tons of broken packages…
-
@timconsidine … but then you get very close to Yunohost and the like that have tons of broken packages…
@necrevistonnezr TRUE. This renders the entire effort suspect. I don't bother using YH anymore, not even to try things out. It'd be a shame if that happens to Cloudron.
-
@timconsidine … but then you get very close to Yunohost and the like that have tons of broken packages…
@necrevistonnezr yes, a risk that must be guarded against
-
@necrevistonnezr TRUE. This renders the entire effort suspect. I don't bother using YH anymore, not even to try things out. It'd be a shame if that happens to Cloudron.
-
The current state of the package:
- building from source not using the official docker image
- photos works (finally)
- other apps (cast/auth/accounts) do not yet
- working on a script that will send the OTP via E-Mail instead of having to retrieve from the logs
- my s3 configuration is still hardcoded because making it work was a pain
-
Oh very nice progress! So ente also has a requirement for an S3 storage without a fallback to the filesystem?
@nebulon correct, ente does not support any other storage options besides s3
-
Oh very nice progress! So ente also has a requirement for an S3 storage without a fallback to the filesystem?
Oh very nice progress! So ente also has a requirement for an S3 storage without a fallback to the filesystem?
Given this seems (annoyingly) increasingly common, perhaps there needs to be a way for Cloudron users to add details of/ configure their preferred S3 storage option to Cloudron which could then be automagically used like an addon for all such apps?
If that is even possible? I guess something like (or even an extension of) Volumes for for S3?
-
Sounds like bundling headless rustS3 would help.
Not sure how Cloudron 9 can handle installing an app w/o another app present, having to check prerequisites.
Easy option is to just include an S3 service like PG integrated into the Cloudron base install. It's common enough now it makes sense.