1
0
mirror of https://github.com/ArcticFoxes-net/Signal-TLS-Proxy synced 2024-11-18 01:41:34 -05:00

Merge remote-tracking branch 'upstream'

Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2022-09-22 21:52:55 -04:00
commit e8ffa5947d
No known key found for this signature in database
GPG Key ID: 060B29EB996BD9F2
3 changed files with 17 additions and 2 deletions

View File

@ -1,6 +1,6 @@
# Signal TLS Proxy
To run a Signal TLS proxy, you will need a host with a domain name that has ports 80 and 443 available.
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.
1. Install docker and docker-compose (`apt update && apt install docker docker-compose`)
1. Ensure your current user has access to docker (`adduser $USER docker`)
@ -9,3 +9,13 @@ To run a Signal TLS proxy, you will need a host with a domain name that has port
1. `docker-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:
```shell
git pull
docker-compose down
docker-compose up --detach
```

View File

@ -10,7 +10,11 @@ http {
listen 80;
location /.well-known/acme-challenge/ {
root /var/www/certbot;
alias /var/www/certbot/;
}
location / {
return 404;
}
}
}

View File

@ -11,6 +11,7 @@ services:
read_only: true
ports:
- "443:443"
- "80:80"
security_opt:
- no-new-privileges:true
cap_drop: