Skip to content
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

Update ngrok zap #13083

Closed
wants to merge 1 commit into from
Closed

Update ngrok zap #13083

wants to merge 1 commit into from

Conversation

adidalal
Copy link
Contributor

@adidalal adidalal commented Aug 8, 2015

Adds zap config for ngrok

Progress on #8202

Adds zap config for ngrok
@@ -9,6 +9,6 @@

binary 'ngrok'

# todo verify that this does not contain user-created content
# zap :delete => '~/.ngrok'
zap :delete => '~/.ngrok2/ngrok.yml',
Copy link
Member

Choose a reason for hiding this comment

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

Why not leave it as in the comment?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ngrok was updated to version 2, and with that, the config structure changed

"ngrok's configuration file format has been redesigned to be simpler and expose more options. The configuration file for 2.0 is a simple YAML file read by default from $HOME/.ngrok2/ngrok.yml"

See: https://ngrok.com/whatsnew

Copy link
Member

Choose a reason for hiding this comment

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

To clarify, what I meant is, why not leave simply as zap :delete => '~/.ngrok2? Why remove the file and then the directory only if it’s empty?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The user can have multiple configurations stored there, but needs to manually create any besides ngrok.yml, so I thought that would fall under "user-generated content"

Copy link
Member

Choose a reason for hiding this comment

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

Ah, no, we discussed that and came to the conclusion zap should remove everything.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay, then just the delete should be fine to merge in

@vitorgalvao
Copy link
Member

Thank you for the contribution. It needed some fixes, so they were made in 6295e11. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

@vitorgalvao vitorgalvao closed this Aug 8, 2015
@adidalal adidalal deleted the patch-1 branch August 8, 2015 14:32
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants