Now let’s see it in action! Using the 1Password ngrok shell plugin Most people will ant to start here but I’d recommend the second per-directory approach for project-level isolation.ĭo the above for each credential you have and then delete those credentials from your ngrok.yml file.

Finally, you can have the plugin use this credential as the global default.

It’s a simple way to keep your projects’ environments separate and not accidentally reset a token and surprise yourself. If you have multiple projects, this is the choice for you.

Second, we can have the plugin automatically use this credential for this directory and all of its subdirectories.

This is what I use so I can operate between different accounts easily but this probably isn’t the choice for you.

First, we can have the plugin prompt us on which credential to use every time we start a new shell.

The is the most powerful part and has three options: Then we provide the authtoken, name it, decide which vault we put it in, and finally specify the scope. We’ll skip to that last step here.Īnd you should get this interface to add your authtoken to the vault: There's a guide to the 1Password CLI integration for the detailed steps but at the highest levels, we have to install the 1Password app, install the 1Password CLI, connect the two, and then initialize the ngrok plugin.

Setting up the 1Password ngrok shell plugin I can seamlessly move between my work and personal laptops - and even reset my authtoken - without having to update it in each location. Not only does this make my demos safer but it keeps credentials synchronized between machines without messaging myself or having to setup my environment twice. Then when you run the familiar: ngrok http 80 you authenticate into your 1Password vault, choose the authtoken you need, and the shell plugin loads the authtoken into memory for you. With the 1Password ngrok shell plugin, instead of keeping your ngrok credentials in a local ngrok.yml file, you store them in 1Password. While editing my ngrok.yml file each time was an approach, it was manual, annoying, and required having my credentials on screen which made for risky demos. Either way, I end up with the problem of juggling multiple credentials in my local environment. More importantly, I’ve started using our Bot Users capabilities to have separate projects within the same account. As a longtime ngrok user, I have a couple different accounts for different projects.

1password business pricing