Skip to content

Conversation

@jsiebens
Copy link
Owner

fixes #2
fixes #3

# inlets-on-fly

inlets-on-fly automates the task of creating an [inlets Pro](https://inlets.dev) exit-server (tunnel server) on the [fly.io](https://fly.io) platform.
inlets-on-fly automates the task of creating an [inlets Pro](https://inlets.dev) HTTP exit-server (tunnel server) on the [fly.io](https://fly.io) platform.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used this to create a TCP exit server previously, so that I could expose SSH. Having TCP would make it useful for inlets-operator too.


if hostStatus.Status == "active" {
if tcp {
fmt.Printf(`inlets Pro TCP (%s) server summary:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this could be back-ported into the cloud-provision library, then perhaps it could be used from inletsctl and inlets-operator, making having to print custom messages etc redundant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can't run this tool more than once on MacOS Convert to machines API instead of flyctl?

3 participants