Mess errors out when Foundry is run behind reverse proxy in a subdirectory
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I just setup my nginx reverse proxy on top of foundry with foundry set up in a subdirectory of my domain. Now the Mess module is broken because it's trying to access the file at systems/dnd5e/module/pixi/ability-template.js but which nginx is sending to https://MYHOST.THISISBROKEN/systems/dnd5e/module/pixi/ability-template.js instead of https://MYHOST.THISISBROKEN/foundry/systems/dnd5e/module/pixi/ability-template.js.
I believe this is a very simple fix, if you just change the import on line 102 in /scripts/modify-templates.js to be a relative import like
const importedJS = (await import(/* webpackIgnore: true */ '../../../systems/dnd5e/module/pixi/ability-template.js'))
Then everything should work a bit smoother.
Contributor guide
No contributing guide indexed for this repository
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 at line 102 of /scripts/modify-templates.js and inspect how the dynamic import resolves the dnd5e ability-template.js path. Verify the resulting import works when Foundry is served from a subdirectory such as /foundry, with the file requested under that prefixed path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100