Ente.io server self host

[phillxnet]

As from 1st March ente.io has fully open sourced it's entire services - backend included:

https://ente.io/blog/open-sourcing-our-server/

Their 'thing' seems to be a privacy focused GPhotos replacement, and they also have a 2FA auth app/server setup - with pending desktop app for the same soon. All have Web-UI and Android/IOS apps: again all open source and available on the respective stores.

Curiously their 2FA auth and photos servers appear to be simultaneous/integrated. So that may prove tricky for a Rockstor rock-on setup. But just noting some key links here in case this is of interest to folks who want to step up re a Rock-on definition contribution:

• https://github.com/ente-io/ente
• https://help.ente.io/self-hosting/
• https://github.com/ente-io/ente/blob/main/server/docs/docker.md

Note that the last link is to their newly presented pre-build docker image: the likely target here for a Rock-on implementation.

[phillxnet]

Just noting here that Ente now offers a free plan with up to 5GB: https://ente.io/#pricing

[Hooverdan96]

doing some investigation on this one. two questions, likely for @FroggyFlox , though @phillxnet might have come across this when working on other Rockon PRs:
Using the docker compose file as guideline: compose.yaml

1. I can see the museum server requires a volume mapping to an (in one case) initially empty config file:

      - ./museum.yaml:/museum.yaml:ro
      - ./scripts/compose/credentials.yaml:/credentials.yaml:ro

Easy enough to set these up prior to installing the Rockon. However for volumes that can be user configured, in the current state we can only enter shares, but not specific files for mapping. So, what to do? Hard-code (and make that a pre-requisite) a share/file combo that a user has to set up prior to installing the rockon? Currently, seems to be the simplest way to handle it.

2. for the minio-mc piece:
   firstly, the same volume mapping for a specific file:

- ./scripts/compose/minio-provision.sh:/provision.sh:ro

and then there is an entrypoint defined:

    entrypoint: sh /provision.sh

I assume, in docker run speak one would need to start the container (oversimplified) like this:

docker run -it --entrypoint='/bin/sh /provision.sh' minio/mc

Correct?
Would one need to add this into the commands section?
(optional)"cmd_arguments": [ An array of cmd_arguments objects that represent arguments to pass to the 'docker run' command] having this format looking like this: ["argument1", "argument2="text2"]