Ngrok container is a thing that can save you a decent amount of time during the third-party integrations’ development process. Feel welcome to get acknowledged with the documentation on the official website.
ngrok container provides an opportunity to get your application tunnelled from your
localhost to a remote
ngrok domain, which is cost-free for up to 8 hours and is convenient to enter into any API that should whitelist you explicitly.
Make sure your Docker setup is relevant - it should have a
docker-compose.ngrok.yml file provided. If you don’t see this file - try simply migrating this single file from the latest Docker setup version.
The only thing necessary here is including the
docker-compose.ngrok.yml file in your startup/teardown sequence.
In order to launch the project with the ngrok container on Linux platform, you should add a new alias to your alias pool. See an example below.
# Having the following aliasalias dcf='docker-compose -f docker-compose.yml -f docker-compose.local.yml -f docker-compose.ssl.yml -f docker-compose.frontend.yml'# Create a new one for startup with the ngrok containeralias dcn='dcf -f docker-compose.ngrok.yml'
In order to launch the project with the ngrok container on Mac platform, you should modify the
mutagen.<...>.yml file(s) which you use to start the application. See an example below.
beforeCreate:- ><....>-f docker-compose.ngrok.ymlup -d --force-recreateafterCreate:- ><....>-f docker-compose.ngrok.ymllogs -f appafterTerminate:- ><....>-f docker-compose.ngrok.ymldown
Start the application using the new alias (Linux) or the updated file (Mac)
Utilise the functionality! See the ngrok usage instructions either inside of that panel or on the official website