nextcloud / nextcloud/notify_push
Setup on environments without systemd
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the service's systemd and Upstart setup requirements against the described Docker, nginx, and Redis deployment. Done would require a defined, documented setup path for environments without systemd, but the issue does not specify the implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, redis
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100