Note in the Settings Page that Metabase Doesn't Formally Support Subpath Deployments
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
What problem will this feature request solve?
We have had customers attempt to use Metabase on sub path deployments and run into trouble because we don't officially support or test sub path deployments. The problem is it's not clear that this isn't supported.
Sometimes customers deploy this way and we find out because they run into product behavior that fails to work as expected (during testing or after upgrade). Or they plan their architecture on the premise they can do this and find out during implementation that it's not a supported approach.
Describe the solution you'd like.
Some in product mechanism to warn people that sub path deployments are not support. Possibly by where the site URL can be set. Not everyone would see it but getting that messaging in front of admin may help in some cases.
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
Start by reviewing the Settings page and the site URL setting mentioned in the issue. Determine where an in-product warning about unsupported subpath deployments could appear, then verify that administrators see clear messaging without changing supported deployment behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100