Setup on environments without systemd

[maximberezin97]

Hi, would it be possible to set up this service if Nextcloud is running in a Docker container? I am running Nextcloud in the linuxserver.io container, which has crontab and init systems available, no Upstart. That container also manages its own internal nginx config. I use an external reverse proxy container called linuxserver/swag which also uses nginx. I also have an external redis container set up for Nextcloud cache/filelocks. My end goal is to achieve performance on the level promised by the high performance backend.

[costalfy]

Hi, have a look at this https://github.com/nextcloud/docker/issues/1422#issuecomment-786481199

[chriham]

I'm running my nextcloud instance and notify_push on a plain linux machine without any docker containers. The system uses OpenRC and has no systemd init system. By starting the notify_push:setup I'm getting

your system doesn't seem to be using systemd.

Yeah, that's true... but why is this required? The notify_push service is already running, redis also. The SetupWizard seems to search for en systemd executable which throws this message. Is this necessary? What can I do on a system running OpenRC?

[ofsahin]

for linuxserver.io's image, an how to add notify push daemon s6 init system tutorial would be nice very poor/hardtounderstand documantation and examples on google for s6

[joshtrichards]

Have you tried checking with the LinuxServer.io community?

https://github.com/linuxserver/docker-nextcloud/issues/194#issuecomment-822045562

Though you might consider running notify_push in it's own Docker image. It already has one.