Container Web Tty Versions Save

Based on v0.1.10, fixed some bugs. And now you can share the same exec ID with others, not only the first one. Besides, I remove the --enable-share flag, and everyone can see what's going on of the TTY if he got the exec link (just share the exec URL to him!).

Yahoo!

Now container-web-tty supports real-time collobarate!

Not only share the input and output of what you are doing but also support the remote user type commands! Thus you can edit the same file at the same time through a same container!

The main purpose of this feature is to interview remotely, there are many online code sharing tools, but none of them support running inside a container, or give you a terminal. So I build this to let you know the candidate better, you can ask him/her create a git repository to test his/her git skills, debug some code issues via gdb, or running his own code via golang, node, gcc, etc. Or even you can check wheter he/she can use vim or emacs!

Later I'll build a website to support this kind of feature: create an interview container -> share to the candidate -> audit the whole interview process -> test his/her skills -> know him/her better!

• update js version (hard work... I know nothing about js)
• remove login shell option, some containers may report mesg: ttyname failed: Success which caused by /root/.profile:mesg n || true
• fix a bug that when you exec your own commands via ?cmd=<your_own_cmd>, the server didn't send ^C to docker daemon, which will cause many useless processes.

It's been a long time for me to update this project, but, enjoy~

• You can share your TTY with others by adding this flag --enable-share, after you exec into that container, your boss/colleague can open that link and see what's happening (real time, and no limit).
• You can enable the history logs in the server side(the user can no nothing about this), so you can see all the inputs and outputs about the containers. (use cat or tail -f is enough, otherwise, you'll see mess characters)
• Some refactor.

• tail logs (just click the container names, supports follow option and tail number option)
• exec your own commands, not just bash/sh/ash only (append the ?cmd=xxx param in the URL, then you will see)

A known issue: I'm not sure I have really fixed #20, but in my case (docker or kubernetes) I didn't meet this situation, if you faced this problem, you can append a comment in that issue and I will see. Please add more details, cause I really have no idea where these characters come from.

It can connect to remote servers to exec into the containers. Use gRPC for connection, support authentication.

Add an --idle-time flag, if the user didn't input something in a fixed time, the connection will close automatically.

Some bug fixes and refactors.

Some refactors and bug-fixes. The main change is container-web-tty removes the docker binary and the kubectl binary from its mounts. I used to use the "local-command exec", but this need the client binary. I refactored it and finally removed them. The container-web-tty's size is 25M(Linux) now, most of it is kubectl's code.

BTW, kubectl's API is not user friendly. Maybe I can make a broker for it.

docker pull wrfly/container-web-tty:0.1.5

• Kubernetes back end
• Container control(with docker)
• More pretty index page

• fix bugs and improve UI
• can pass extra args(e.g. environments)

Anyway, it works.

The binary was built under Linux (Ubuntu 17.04) and tested with 17.05.0-ce