Replace the relative ./sessions bind mount with a Docker-managed named
volume so WhatsApp sessions survive container recreation and redeploys
(e.g. on Dokploy), instead of being reset on every fresh deploy.
* feat: support outbound proxy for Chromium sessions
Routes WhatsApp Web traffic through an HTTP/HTTPS/SOCKS5 proxy when
PROXY_URL is set. Optional PROXY_API_KEY enables auth by passing the
key as the basic-auth username (the format API-key proxies expect).
No behavior change when unset.
Useful for deployments behind egress filters or where outbound
WhatsApp traffic must originate from a specific IP.
* docs: 📝 rewrite proxy auth part
* fix: 🐛 move api key value to passwd
* fix: 💄 change var naming
* fix: 🎨 change var ref in docs and data passing
This fixes#116 by adhering to the newer whatsapp-web.js interface and using 'window.require' instead of 'window.store'
Co-authored-by: nir <nir@severin>
window.Store was removed from whatsapp web. This piece of code was using it still.
I was now getting hit with it once #104 was merged, although I'm not sure why I wasn't earlier.
This might be a bigger issue that needs addressing here, or something that depends on whatsapp web js version
Co-authored-by: nir <nir@severin>
* feat: add reverse proxy support with configurable base path and trust proxy settings
* fix: ensure environment variables are loaded correctly in Docker
- Move dotenv config to the top of server.js
- Update docker-compose.yml to properly handle .env file
- Remove duplicate environment variables section
This ensures BASE_PATH and TRUST_PROXY work as expected in both Docker and local environments.
* refactor: remove hardcoded environment variables from docker-compose.yml
* feat: Allow host port to be configured via .env
* feat: add reverse proxy support with configurable base path and trust proxy settings
* fix: ensure environment variables are loaded correctly in Docker
- Move dotenv config to the top of server.js
- Update docker-compose.yml to properly handle .env file
- Remove duplicate environment variables section
This ensures BASE_PATH and TRUST_PROXY work as expected in both Docker and local environments.
* refactor: remove hardcoded environment variables from docker-compose.yml
* feat: add reverse proxy support with configurable base path and trust proxy settings
* fix: ensure environment variables are loaded correctly in Docker
- Move dotenv config to the top of server.js
- Update docker-compose.yml to properly handle .env file
- Remove duplicate environment variables section
This ensures BASE_PATH and TRUST_PROXY work as expected in both Docker and local environments.
