WeTTY provides the ability to run terminals in a browser and is an upgraded alternative to Ajaxterm and Anyterm. Compared to them, WeTTY has a better experience because it is based on xterm.js, a fully functional JavaScript terminal emulation library. At the same time, it communicates through WebSocket rather than traditional Ajax, resulting in a faster, smoother response experience. functional properties 1. Terminal access within browser (HTTP/HTTPS) WeTTY integrates terminals (TTY) into web pages, allowing users to remotely access the terminal interface through a browser, and supports HTTP and HTTPS protocols. 2. Complete terminal simulation based on xterm.js Xterm.js implemented using JavaScript provides highly reversible terminal emulation capabilities that are superior to traditional Ajaxterm and Anyterm. 3. Use WebSockets for real-time interactions and faster response times Compared with the Ajax-based approach, the WebSockets connection method makes terminal interactions smoother and lower latency. 4. Version and configuration support Provides--help and--version options to make it easy to view help information and current version number. 5. Support loading configuration files You can specify the configuration file path through--conf to load running parameters from the configuration file. 6. HTTPS support Support the use of--ssl-key and--ssl-cert to specify SSL private keys and certificates, thereby enabling HTTPS secure connections. 7. Flexible SSH login options · --ssh-host: Specify the target SSH server host; · --ssh-port: Specify the SSH service port; · --ssh-user: Specifies the username used to log in. 8. Supports multiple SSH authentication methods Specify the authentication method through--ssh-auth (the default is "password", or you can also configure it such as "publickey,password"); --ssh-pass can be used to specify the SSH password; --ssh-key can provide the client's private key to realize secret-free connection. 9. Customize SSH configuration You can use--ssh-config to specify instead of the default ssh configuration file to achieve more flexible use of SSH. 10. Forced SSH connection method Use--force-ssh to force connections through SSH even as root rather than using local login. 11. Known host file support Use--known-hosts to specify the known_hosts file path to strengthen SSH security. 12. Page path and port configurable · --base (or-b) Specifies the base path of WeTTY; · --port (or-p) Specifies the port on which the server listens; · --host can specify the host address to listen on. 13. Customize command execution capabilities You can specify that custom commands are executed in the shell context through--command (or-c). 14. Allow embedding iframe Use--allow-iframe to allow WeTTY to be embedded in iframe (only same-origin embedding is allowed by default). 15. Automatic user login path support Users <username>can directly specify the login user name by visiting http://yourserver:3000/wetty/ssh/, simplifying the operation process. 16. Default behavior description · If you run with root privileges,/bin/login will be launched, allowing users to enter their username; · If ordinary users are running it, they will connect to localhost via SSH by default. 17. Docker container support Provide Docker images. An example of running method is docker run --rm -p3000:3000 wettyoss/wetty --ssh-host=<YOUR-IP>, which supports rapid deployment of WeTTY services. 18. Recommended use of reverse proxies to improve security Deploying WeTTY behind reverse proxies such as nginx-proxy or traefik provides secure access to HTTPS and supports Let's Encrypt automated certificate management. 19. Specific container configuration examples provide Traefik's docker-compose example is provided under the containers directory, showing how to integrate WeTTY with reverse proxies. 20. browser compatibility Supports all browsers supported by xterm.js with wide compatibility.
