feat: add subpath config #1236
feat: add subpath config #1236
Conversation
|
|
@datnguyennnx is attempting to deploy a commit to the HyperDX Team on Vercel. A member of the Team first needs to authorize it. |
| HYPERDX_LOG_LEVEL=debug | ||
| EXPRESS_SESSION_SECRET="hyperdx is cool 👋" | ||
| FRONTEND_URL="http://localhost:${HYPERDX_APP_PORT}" | ||
| FRONTEND_URL="http://localhost:4040/hyperdx" |
There was a problem hiding this comment.
we don't need to update this unless devs want to test out the proxy
| }); | ||
|
|
||
| module.exports = { | ||
| basePath: process.env.HYPERDX_BASE_PATH || '', |
There was a problem hiding this comment.
Let's call it NEXT_PUBLIC_BASE_PATH. We also need to verify if this works on production build
| HYPERDX_APP_URL=http://localhost | ||
| HYPERDX_LOG_LEVEL=debug | ||
| HYPERDX_OPAMP_PORT=4320 | ||
| HYPERDX_BASE_PATH=/hyperdx |
There was a problem hiding this comment.
Let's roll this back since it affects prod
| @@ -0,0 +1,35 @@ | |||
| http: | |||
There was a problem hiding this comment.
Can you add a README file to proxy directory to explain what it’s about? It would also be helpful to mention NEXT_PUBLIC_BASE_PATH and FRONTEND_URL env vars
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Introduce the new flag NEXT_PUBLIC_BASEPATH to simplify subpath configuration for HyperDX deployments. Builds on the flexible basePath config added in [PR #1188], making it easier to handle frontend routing under custom subpaths using an environment variable. Proxy configuration examples for nginx and Traefik will also be provided for reference.