silberengel
/
jumble
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1770 Commits
1 Branch
0 Tags
73 MiB
 
 
 
 
Tree: 84ebb7bdb1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '84ebb7bdb1'
${ noResults }
jumble/PROXY_SETUP.md

1.3 KiB
Raw Blame History

Proxy Setup

Imwald uses same-origin proxy paths in production so browsers do not need cross-origin CORS exceptions.

Link Preview / RSS Proxy

Set VITE_PROXY_SERVER at build time. The current client contract is:

${VITE_PROXY_SERVER}/sites/?url=<encoded-url>

For the public deployment this is normally:

VITE_PROXY_SERVER=https://jumble.imwald.eu

Apache/nginx should route /sites/ to the OG proxy container, before the SPA catch-all.

Apache example:

ProxyPass        /sites/ http://127.0.0.1:8090/sites/
ProxyPassReverse /sites/ http://127.0.0.1:8090/sites/
ProxyPass        / http://127.0.0.1:8089/
ProxyPassReverse / http://127.0.0.1:8089/

Optional Same-Origin APIs

These are enabled by build-time URLs:

VITE_READ_ALOUD_TTS_URL=/api/piper-tts
VITE_LANGUAGE_TOOL_URL=/api/languagetool
VITE_TRANSLATE_URL=/api/translate

Proxy targets:

ProxyPass        /api/piper-tts http://127.0.0.1:9876/api/piper-tts
ProxyPassReverse /api/piper-tts http://127.0.0.1:9876/api/piper-tts
ProxyPass        /api/languagetool http://127.0.0.1:8010
ProxyPassReverse /api/languagetool http://127.0.0.1:8010
ProxyPass        /api/translate http://127.0.0.1:5000
ProxyPassReverse /api/translate http://127.0.0.1:5000

For the full production workflow, use scripts/README-deploy.md and docker-compose.prod.yml.