We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If we want to run notify behind a proxy server on a path such as /notify/ currently it doesn't work.
Setup a server such as (caddy)[https://caddyserver.com/download]
Using a Caddyfile config like this...
:7007 { respond "This request didn't make it to notify, sorry" redir /notify /notify/ handle_path /notify/* { reverse_proxy http://localhost:8007 } }
Steps to reproduce the behaviour:
Should be able to run notify on this path (perhaps with a config change?)
This stack overflow suggests using a public path publicPath: '/app' https://stackoverflow.com/questions/63674303/configure-webpack-to-serve-react-at-relative-path
publicPath: '/app'
Maybe we set it up to always run on /notify/?
The text was updated successfully, but these errors were encountered:
jmbrunskill
lache-melvin
Successfully merging a pull request may close this issue.
Describe the bug
If we want to run notify behind a proxy server on a path such as /notify/ currently it doesn't work.
To Reproduce
Setup a server such as (caddy)[https://caddyserver.com/download]
Using a Caddyfile config like this...
Steps to reproduce the behaviour:
Expected behaviour
Should be able to run notify on this path (perhaps with a config change?)
Additional context
This stack overflow suggests using a public path
publicPath: '/app'
https://stackoverflow.com/questions/63674303/configure-webpack-to-serve-react-at-relative-path
Maybe we set it up to always run on /notify/?
The text was updated successfully, but these errors were encountered: