Tested with a build and creating a new exit-server on DO.
I connected an inlets 0.9.1 client to it and accessed the built-in fileserver and accessed it via the DO IP address.
# Create the tunnel server
./inletsctl create --access-token-file ~/token
# Run the tunnel command
# Give a single value or comma-separated
export PORTS="8000"
# Where to route traffic from the inlets server
export UPSTREAM="localhost"
inlets-pro tcp client --url "wss://167.172.59.143:8123" \
--token "token..." \
--upstream $UPSTREAM \
--ports $PORTS
# Run a local server process
mkdir /tmp/test
cd /tmp/test/
touch hi
inlets-pro fileserver -w ./ -a -p 8000
# Access it via the tunnel
curl 167.172.59.143:8000
2021/10/27 15:36:19 Request: 167.172.59.143:8000 / [899d9fbb-ae47-42d7-b75a-f3594ddb52c8]
2021/10/27 15:36:19 Sent . (4.1 kB) [899d9fbb-ae47-42d7-b75a-f3594ddb52c8]
<pre>
<a href="hi">hi</a>
</pre>
# Delete the tunnel
./inletsctl delete --access-token-file ~/token --ip 167.172.59.143
How are existing users impacted? What migration steps/scripts do we need?
Fixes #114
Existing users should not be affected.
Checklist:
I have:
[x] updated the documentation and/or roadmap (if required)
Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com
Description
Bump inletsctl version to 0.9.1
How Has This Been Tested?
Tested with a build and creating a new exit-server on DO.
I connected an inlets 0.9.1 client to it and accessed the built-in fileserver and accessed it via the DO IP address.
How are existing users impacted? What migration steps/scripts do we need?
Fixes #114
Existing users should not be affected.
Checklist:
I have:
git commit -s