inlets/inletsctl

[Feature] install client with systemd

alexellis opened this issue · 1 comments

Expected Behaviour

Given a remote URL, upstream and auth token, users should be able install a systemd unit file so that their tunnel persists.

Current Behaviour

Needs to be done manually or ad-hoc

Possible Solution

Copy approach from faasd - https://github.com/alexellis/faasd/blob/master/cmd/install.go

Steps to Reproduce (for bugs)

Workflow:

  1. inletsctl create (observe the output)
  2. inletsctl install --remote x --upstream y --token z
  3. systemctl status inlets

Context

For users who need a permanent tunnel from a Linux laptop, VM, bare-metal on-prem host or RPi, this is going to make running the client much easier for them.

Also related #12

This has been added to inlets-pro as a feature, but is relatively straight-forward for folks to write-up, the example in the repo for the server can be copied / adapted.

https://github.com/inlets/inlets-pro/releases/tag/0.5.4