8ce3947d7d
Bumps certbot/certbot from `78a7eaa` to `0107d08`. --- updated-dependencies: - dependency-name: certbot/certbot dependency-version: 0107d084c225631fc64a8313e19adb07275f7296fde338f7dfa93986c80b2e3e dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| .github | ||
| data | ||
| .gitignore | ||
| docker-compose.yml | ||
| init-certificate.sh | ||
| LICENSE | ||
| README.md | ||
Signal TLS Proxy
To run a Signal TLS proxy, you will need a host that has ports 80 and 443 available and a domain name that points to that host.
- Install Docker by following the instructions at https://docs.docker.com/engine/install/
- Clone this repository
./init-certificate.shdocker compose up --detach
Your proxy is now running! You can share this with the URL https://signal.tube/#<your_host_name>
Updating from a previous version
If you've previously run a proxy, please update to the most recent version by pulling the most recent changes from main, then restarting your Docker containers:
git pull
docker compose down
docker compose build
docker compose up --detach
Stability Policy
We endeavor to provide updates to this repository thirty days in advance of them being required to use the Signal service, but may not always be able to do so for operational reasons. Proxy operators are advised to please check for updates at least once every thirty days, if not more often. You may use the instructions above to update as needed.
Contributions welcome
We want this proxy to be simple to deploy for a broad population, but we know that it won’t fit all deployments—especially advanced users that already have running servers or specific technology preferences. We welcome contributions that make incremental improvements, updates, and improve compatibility, but aren’t considering significant architectural changes.