follow-ups for community-containers

[szaimen]

Follow-ups for #1581

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?
• allow to add documentation link on the additional containers (male name clickable) allow to add documentation on containers #3478
• allow to define nextcloud_variables
• allow to define nextcloud_secrets
  • adjust Request to add pdlib to PECL. goodspb/pdlib#56 and Add container to AIOs community containers to make configuration for them easier matiasdelellis/facerecognition-external-model#8 if both are available
• allow to back up empty additional volumes #3642
• Add
  • makemkv (use https://github.com/jlesage/docker-makemkv)?
  • add libretranslate and integration https://github.com/LibreTranslate/LibreTranslate/blob/main/docker/Dockerfile https://github.com/LibreTranslate/LibreTranslate/blob/main/docker-compose.yml (afterwards redo add notice regarding AIO translate#33) initial commit szaimen/aio-libretranslate#1 update to Nc27 v1r0x/integration_libretranslate#1
  • vaultwarden https://github.com/nextcloud/vm/blob/9f58a314955bf402ba36b3c78f4717331cc58e6e/apps/vaultwarden.sh#L239-L255 community-containers - add vaultwarden #3455
  • local ai container? Allow to upload the models via nextcloud itself community containers - add local ai #3495
  • plex community-containers - add plex #3439
  • caddy with geoblocking https://github.com/porech/caddy-maxmind-geolocation allow to set aio_variables from containers.json #3459 community-containers - add caddy #3460
  • pihole https://github.com/pi-hole/docker-pi-hole/ community-containers - add pi-hole #3456
  • pivpn? (use fritzbox?)
  • fail2ban community-containers - add fail2ban as example container for testing purposes #2637
• 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. (maybe base it on top of https://github.com/jlesage? add license? jlesage/docker-baseimage-gui#113
  • smbserver https://github.com/nextcloud/vm/blob/master/not-supported/smbserver.sh (maybe base it on top of https://github.com/jlesage? add license? jlesage/docker-baseimage-gui#113)
• add on the fly notification? Maybe get notificcations via nc into the nc container and then use the admin notify scirpt...
  • add off-shore backup container afterwards for regular backups -> needs to be able to notify of failed or succesful backup
• allow to define if a secret gets shown in the aio interface and also allow to add a description for a secret and also allow to add a description of what the token does
• allow to set not defined environmental variables from the aio interface: by providing an input field and regex and maybe even description).
• allow to define custom cronjobs already possible via nextcloud_exec_commands

community could add

• netdata (add an example json to the request)
• pgadmin (add an example json to the request)
• jellyfin (addn an example json to the request)
• Scrutiny (addn an example json to the request)
• lldap (should only set this one up, nothing more but add good docs how to configure nextcloud, maddy ans maybe even vaultwarden? to use it); interface should be limited to apache_ip_bindin, ldap not exposed on host); interface should be available via its own domain protected by geoblocking also add link to discussinoo to readme then
• docker-mailserver (add an example json to the request) also add link to discussion to readme then
• mail server (add an example json to the request) also add link to discussion to readme then
• more?

[szaimen]

Follow-ups 2 in #3889

[jakobroehrl]

Maybe we can add

• uptime_kuma https://github.com/louislam/uptime-kuma and
• a dashboard/startpage like https://github.com/pawelmalak/flame or https://github.com/bastienwirtz/homer

[szaimen]

• uptime_kuma https://github.com/louislam/uptime-kuma and

Not sure how sensible this is when it runs on the same server

• a dashboard/startpage like https://github.com/pawelmalak/flame or https://github.com/bastienwirtz/homer

this sounds more useful. Feel free to suggest it via https://github.com/nextcloud/all-in-one/discussions/new?category=ideas