nextcloud / nextcloud/whiteboard
haproxy configuration
Open
Nobody has claimed this yet.
documentation
good first issue
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
In the README you provide an apache, nginx and cadet configuration, here is yet another one:
frontend <your-domain>
bind ...
...
acl is_whiteboard path_beg -i /whiteboard
use_backend whiteboard if is_whiteboard
...
backend whiteboard
mode http
option forwardfor
option http-server-close
http-request replace-path /whiteboard(/)?(.*) /\2
timeout tunnel 1h
http-request set-header Connection "Upgrade"
http-request set-header Upgrade %[req.hdr(Upgrade)]
server whiteboard 192.168.0.1:3002 check # your internal IP address and port, here default whiteboard port
Uses <your_domain>/whiteboard as path (so you configure with /whiteboard), removes it and forwards connection to whiteboard server. Take a look at sticky sessions if you want to add more whiteboard servers
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
Update the README alongside its existing Apache, nginx, and Cadet configuration examples. Add the supplied HAProxy configuration for serving the whiteboard under /whiteboard, then check that the example matches the documented default port and path; the issue is done when the HAProxy setup is included clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100