How amirmohammaddsht-dev/backpack-railway works
Backpack-Railway packages a BackPack tunnel and a 3x-ui panel for deployment on Railway or Fly.io. The main workflow is to create a tunnel on the Iran server, provide its setup link and panel credentials as deployment variables, then use the tunnel to deliver traffic to a 3x-ui inbound. The container also exposes a secret-path BackPack status/log panel and a watchdog for tunnel recovery. Relationships below follow the README; source excerpts were not provided, so internal script-level calls are not inferred.
Main entry points: entrypoint.sh Application container · apply-link.sh Setup-link application · supervisord.conf Process supervisor
Components 13
Deployment and startup
- Application container
entrypoint.sh - Process supervisor
supervisord.conf
Tunnel connectivity
- Setup-link application
apply-link.sh - BackPack tunnel
Panels and traffic
- 3x-ui panel and inbounds
- Panel configuration
panel-config.sh - BackPack web panel
Tunnel reliability
- Tunnel watchdog
- Systemctl shim
fake_systemctl.sh - Journal shim
fake_journalctl.sh
Other components
- Operator
- Railway / Fly.io
- Iran server
Connections 13
- Operator → Iran server: creates tunnel
README.md - Iran server → Operator: provides setup link
README.md - Operator → Railway / Fly.io: deploys and configures
README.md - Railway / Fly.io → Application container: runs deployment
README.md - Operator → Application container: supplies setup link
README.md - Application container → Iran server: dials out
README.md - Application container → Setup-link application: applies link
- Setup-link application → BackPack tunnel: configures tunnel
- BackPack tunnel → 3x-ui panel and inbounds: delivers traffic
README.md - Operator → 3x-ui panel and inbounds: creates inbounds
README.md - Operator → BackPack web panel: checks status and logs
README.md - Tunnel watchdog → BackPack tunnel: restarts tunnel
README.md - Process supervisor → Tunnel watchdog: keeps running