Saved tunnel configs
currently the saving and loading tunnel configs is adhoc - by specifying a path to a single config file. we need to store and list all tunnel configs from a single location - ideally app and cli both should use this common location
How to auto start tunnels from CLI when the CLI starts?
There should be two steps -> (1) one mark tunnel configs to auto start. (2) add a --auto-start-tunnels to automatically start the tunnel configs which are marked to auto start.
Like:
./pinggy --remote-management --auto-start-tunnels # will automatically start remote management as well as some of the tunnels
./pinggy --save --name "my tunnel" -p443 -L0:localhost:4300 -R0:localhost:8000 -Rtcp//domain.com/2344:2344:localhost:3456 token@pro.pinggy.io
./pinggy --config-list # or -ls
configid name remote -> https://localhost:8000, tcp://domain.com:2344->tcp://localhost:3456
./pinggy --auto-start configid
./pinggy -ls
configid name remote -> https://localhost:8000, tcp://domain.com:2344->tcp://localhost:3456 [auto start]
./pinggy --auto-start-tunnels
Starting tunnel configid1 .....
Starting tunnel configid2 .....
For auto start, we will not render tui -> logic is if there are multiple tunnels possible - do not render TUI. same happens for remote management.
Where do we save the list of auto starting tunnels?
Saved tunnel configs
currently the saving and loading tunnel configs is adhoc - by specifying a path to a single config file. we need to store and list all tunnel configs from a single location - ideally app and cli both should use this common location
How to auto start tunnels from CLI when the CLI starts?
There should be two steps -> (1) one mark tunnel configs to auto start. (2) add a
--auto-start-tunnelsto automatically start the tunnel configs which are marked to auto start.Like:
For auto start, we will not render tui -> logic is if there are multiple tunnels possible - do not render TUI. same happens for remote management.
Where do we save the list of auto starting tunnels?