- Rust 72.5%
- Nix 27.5%
| .forgejo/workflows | ||
| src | ||
| .envrc | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| docker.nix | ||
| flake.lock | ||
| flake.nix | ||
| module.nix | ||
| overlay.nix | ||
| package.nix | ||
| README.md | ||
Tasproxy
Auto-discovery reverse proxy for tasmota
Why
Remembering what ip addresses all of your tasmota devices is a pain.
Setup
Ensure your tasmota devices are connected to an MQTT server with the following "Full Topic":
%prefix%/%topic%/
And the "Topic" set to the desired name for the device.
Run the binary with the following environment variables
MQTT_HOSTNAME: hostname of the MQTT server to connect toMQTT_PORT: port of the mqtt server to connect to, defaults to 1883MQTT_USERNAME: username to authenticate against the mqtt serverMQTT_PASSWORD: password to authenticate against the mqtt serverPORT: port this binary MQTT listen on, defaults to 80
You can also configure the proxy to send HTTP Basic authentication to the
tasmota devices by setting the TASMOTA_USERNAME and TASMOTA_PASSWORD
environment variables.
Setup dns/hosts/etc to point *.example.com to the server running this binary
Usage
The proxy server will use MQTT to discover and gather the ip addresses of your tasmota devices.
Any request made to %hostname%.example.com will be proxied to the tasmota
device with the corresponding topic.