Ente for cloudron, help for testing wanted.

[andreasdueren]

I have a working package of ente for cloudron.

You can use my docker image with andreasdueren/ente-cloudron --tag 0.4.5

Currently these are the limitations/quirks:

• admins need to manually set up Aliases for the following sub domains: family, albums, cast, auth and accounts
• the actual user IP addresses aren't passed into the log by caddy. Right now the Dockerfile installs the Debian-packaged Caddy that ships with cloudron/base:5.0.0, which is why the optional modules aren’t present. If we want http.handlers.realip, we would need to build Caddy ourselves and bundle that binary instead of apt-getting the stock one.
• I have only tested this package with one s3 zone. Replication should be working but I haven't had time to test it.
• In general this application relies heavily on the CLI for user management. This includes increasing storage quota. It should work, but again haven't had much time to test.

[andreasdueren]

I think this is ready for an unstable release: andreasdueren/ente-cloudron:0.5.3

I tested and fixed:

• Upload with the mobile app
• The CLI/increasing storage quota
• httpPorts feature for automatic sub domain setup

[necrevistonnezr]

Is the manual setup of subdomains still required after https://forum.cloudron.io/post/114771?

[andreasdueren]

@necrevistonnezr Nope

[andreasdueren]

Updated Ente Package: andreasdueren/ente-cloudron:0.5.5

• Implemented replication across three buckets

Tested with the following providers:

Primary: Backblaze, Secondary: Hetzner Object Sorage, Glacier: Scaleway

One important consideration: The cold bucket needs to support the GLACIER class Ente tries to use. So either point S3_COLD_* at an actual Glacier-capable object store (like Scaleway’s cold tier) or switch the app to local buckets mode so the start script configures Museum with are_local_buckets: true / use_path_style_urls: true, which causes the replication controller to skip the Glacier storage class.