Archives
/
tty-proxy
mirror of https://github.com/elisescu/tty-proxy/
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3 Commits
2 Branches
2 Tags
1.2 MiB
Go 95.1%
CSS 3%
HTML 1%
Dockerfile 0.9%
 
 
 
 
master
test-action
v0.0.1
v0.0.2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '385b8e171c'
${ noResults }
Go to file
Vasile Popescu 385b8e171c Udate the Dockerfile and README 
The previous commits comes directly as Thomas added it to the tty-server
project, and this commits adapts them to this project. They are pretty
similar but not quite the same.
 		4 years ago
static Initial commit 4 years ago
vendor Initial commit 4 years ago
.gitignore Initial commit 4 years ago
Dockerfile Udate the Dockerfile and README 4 years ago
README.md Udate the Dockerfile and README 4 years ago
go.mod Initial commit 4 years ago
go.sum Initial commit 4 years ago
gobindata.go Initial commit 4 years ago
journal.org Initial commit 4 years ago
main.go Initial commit 4 years ago
server.go Initial commit 4 years ago

README.md

tty-proxy

Building the gobindata.go file

All files under ~assets/*~ are packed to the gobindata.go file which will be statically compiled within the final binary.

	go get github.com/go-bindata/go-bindata/...
	go-bindata --prefix static -o gobindata.go static/*

Docker

The tty-proxy can be built into a docker image as follows:

docker build -t tty-proxy .

To run the container, type:p

docker run \
  -p 3456:3456 -p 8080:8080 \
  -e URL=http://localhost:8080 \
  --cap-drop=all --rm \
  tty-proxy

where you can replace URL by whatever will be the publicly visible URL of the server.

After this, clients can be connected as follows:

tty-share --tty-proxy localhost:3456 --no-tls --public

In the above command, :3456 is the default port where tty-proxy listens for incoming back connections (i.e. tty-share clients), and 5000 is the port of the web interface through which remote users can connect. You can override the defaults by specifying a different port mapping on the command line, e.g. -p 4567:3456 -p 80:8080 to listen on 4567 and serve on 80.