[bug]: APP_BASE_URL does not change static paths
@vihar is already working on this.
Since Jul 22, 2024.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched the existing issues
Current behavior
I tired to deploy Plane with docker compose, however I wanted to use my own reverse proxy. Since and don't have access to any subdomains, only this one, I'll use on a subpath mydomain.domain.com/plane. Now, multiple apps run in docker behind a reverse proxy and are reachable under a subpath.
Steps to reproduce
Therefore, I modified docker-compose.yaml a bit, and everything goes fine; however, when I try to reach frontend, it gives static path as they are (e.g., _next/static/css/b923f778974e6eb1.css and not plane/_next/static/css/b923f778974e6eb1.css). I set APP_BASE_URL in plane.env, but it seems like it doesn't have any impact on the static routes.
Is there something that I missed or APP_BASE_URL has a completely different purpose? No docs mention it at all.
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
v0.22-dev
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.
Assessment
This issue has not been assessed yet.