notify_push icon indicating copy to clipboard operation
notify_push copied to clipboard

Add support for specifying base path

Open JuniorJPDJ opened this issue 4 years ago • 2 comments

It would be great if while proxying, only routing by path would need to be applied. Adding base path to notify_push would solve that.

Why? For example: https://serverfault.com/a/336784

Example: add env var or cmdline argument to specify base path:

PUSH_BASE_PATH=https://your_nextcloud_address/push

After that you'd only need to route https://your_nextcloud_address/push/* to notify server in reverse proxy.

JuniorJPDJ avatar Jul 11 '21 08:07 JuniorJPDJ

0a14040 doesn't cover this completely but should help with the common case without requiring extra configuration

icewind1991 avatar Jul 12 '21 10:07 icewind1991

It means it will just work with path starting with /push? Cool, I'm deploying then. Anyway would be cool to have base path implemented for more custom deployments, if you will not do this - just close ;D

JuniorJPDJ avatar Jul 14 '21 10:07 JuniorJPDJ