Skip to content

update README.md - #1318

Merged
jeff-bruemmer merged 2 commits into
masterfrom
docs-readme-note
Sep 2, 2026
Merged

update README.md#1318
jeff-bruemmer merged 2 commits into
masterfrom
docs-readme-note

Conversation

@jeff-bruemmer

Copy link
Copy Markdown
Member

Clarified the behavior of METABASE_REPO_PATH and its effect on serving documentation.

Clarified the behavior of METABASE_REPO_PATH and its effect on serving documentation.
@jeff-bruemmer jeff-bruemmer self-assigned this Sep 2, 2026
Comment thread README.md
With `METABASE_REPO_PATH` set, `/docs/latest` serves and hot-reloads files from your local Metabase repo, and only `/latest` routes are available — earlier versions 404. Comment it out to serve all versions from `./_docs` instead.
With `METABASE_REPO_PATH` set, `/docs/latest` serves your current branch (NOT the latest branch), and hot-reloads files from your local Metabase repo. Only `/latest` routes are available, which again, are the docs from whatever branch your Metabase repo is on.

Restart the dev server after changing `.env`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to keep the "Restart the dev server after changing .env." line. At least in my testing, I was changing it a bunch, and it behaved much more predictably if I restarted the dev server after saving .env changes.

Comment thread README.md
@jeff-bruemmer
jeff-bruemmer enabled auto-merge (squash) September 2, 2026 19:23
@jeff-bruemmer
jeff-bruemmer merged commit f60f1da into master Sep 2, 2026
4 checks passed
@jeff-bruemmer
jeff-bruemmer deleted the docs-readme-note branch September 2, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants