Fix dashboard /web Internal Server Error by resolving templates directory to absolute path#117
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
TemplateNotFound(Internal Server Error) when the process CWD was notmaster-api, so templates must be loaded via a stable absolute path.Description
templates = Jinja2Templates(directory="static")to compute an absolute path with_STATIC_DIR = Path(__file__).resolve().parents[2] / "static"and initializeJinja2Templates(directory=str(_STATIC_DIR))inmaster-api/app/core/globals.pyso template loading is independent of process working directory.Testing
python -m py_compile master-api/app/core/globals.pywhich succeeded without syntax errors.PYTHONPATH=master-api python - <<'PY' ...which printed the_STATIC_DIRand confirmed itexists().Codex Task