follow-ups 2 for community-containers

[szaimen]

Follow-ups for #3432

earlier

• think about instance restore: should teh backup container run twice in a row to restore the setting first and then start the correct restore. Same for normal restore? AIO interface: document limitation regarding restoring of community container data #4707
  • remove the beta hint in the docs after this is resolved
• allow to define nextcloud_variables Not needed anymore due to Support multiple substitutions per line for envs in containers.json #6568
• allow to define nextcloud_secrets Not needed anymore due to Support multiple substitutions per line for envs in containers.json #6568
  • adjust

    all-in-one/community-containers/facerecognition/facerecognition.json

    Line 13 in 5cbbe1b

    "API_KEY=some-super-secret-api-key"

    if both are available Done in facerecognition-cc: update json to use actual secret for api key #6835
• instead of modifying container to put a caddy import into place, should there be an option to modify a subpath that is automatically forwarded to the correct container in a subpath available on the nextcloud domain? containers definition - allow to define caddy_routes #3192 (maybe also use that in the containers but must also work without)
  • move onlyoffice to community apps afterwards? (Also remove all onlyoffice logic from aio then) -- needs testing with jwt secret - maxbe sheet with the secret for now...

later

• add containers
  • add backup container that allows to view the backup, restore files, etc. add borgbackup-viewer community container #5889
  • smbserver community-containers: add smb-server #6162
• add on the fly notification? Maybe get notificcations via nc into the nc container and then use the admin notify scirpt... tracked now in community-containers: allow to send on the fly notifications #6836
  • add off-shore backup container afterwards for regular backups -> needs to be able to notify of failed or succesful backup Not a good idea, because it would be stopped by the daily backup feature... So abandoned this idea for now.
  • allow to somehow configure sending notifications szaimen/aio-scrutiny#3
• allow to define if a secret gets shown in the aio interface #5938
• allow to set not defined environmental variables from the aio interface: by providing an input field and regex and maybe even description).

[luzfcb]

It should be good to have an option to pass additional arguments to the docker run command per container. (related to #4277)

https://docs.docker.com/config/containers/resource_constraints/#gpu
https://docs.docker.com/engine/alternative-runtimes/

[szaimen]

Someone started working on that in #5132 but you saw that already

[szaimen]

This is now implemented since a while

[szaimen]

I've added this to the list in #5251 now

[szaimen]

This is mostly done. Tracking remaining task in #6836