-
-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support running without a daemon and without privileged code #318
Comments
would be nice if ET worked more like mosh, as then I could use/more easily adapt the mosh client/server wrappers my company has to make mosh work on their network. on top of not requiring a root daemon |
I suppose having a separate portable client (running without root access) should be even easier to accomplish, and (arguably) more valuable. |
You can run et without root. Check the GitHub actions (continuous integration) to see examples. |
Hi @MisterTea, can you point out the change that closes this issue? I browsed at least a year back (further than I last installed from trunk when I was using ET at my previous employer), and didn't see any significant change to how ET works on the server side, and see that systemctl/et_service and various other system service startup files still exist. The point of this issue was to get rid of etserver, or at least have it run as a regular user, much like mosh works, so that you do not need root on the server machine in order to be able to install/upgrade ET. Or point to a specific GitHub action? There are 35 pages of them... |
Here's examples of etserver running as a regular user: https://github.com/MisterTea/EternalTerminal/blob/master/.circleci/config.yml |
The examples use sudo but I don't think it's necessary as long as you change the ET port to be more than 4096 (unix rule). Please correct me if I'm wrong. |
It would be great if et automatically started the network server as a user from ssh (basically, like what mosh does) rather than using a daemon running as root.
The text was updated successfully, but these errors were encountered: