nextcloud / nextcloud/notify_push
Instructions for "more complex" setups
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
The setup wizard suggests to refer to the manual setup for more complex setups:
If your setup is more complex or involves any kind of load balancing you should follow the manual setup instruction on the README instead
However, the Manual Setup instructions don't go into that.
How would this be set up in a clustered environment where a number of web servers are behind an HA Proxy?
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
Start with the setup wizard wording and the README's Manual Setup section linked in the issue. Investigate how notify_push should be deployed when multiple web servers sit behind HA Proxy, then document the clustered setup and what a working configuration should achieve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100