docsbuild
service is not for public consumption and we would like to view it along with our code deployments in pre-production settings. Normally, the main application is configured with authentication and auth controls, but the docs are just web pages and would be difficult to protect. If you added a regular hostnames:
section to your application, the documentation would be exposed to the internet. Let's create a private tunnel for an additional layer of secrecy.NGROK_AUTH
token is self explanatory, but the rest need to be explained. In this case, the NGROK_LOOK_DOMAIN
is the service to expose via the ngrok tunnel, in this case it would be http://docsbuild
from above. If you were exposing a different port or hostname, adjust as needed. You could consider adding a sidecar and pointing to http://localhost
for even more privacy. The NGROK_BINDTLS
option tells ngrok to only support https:
traffic which is obviously correct.hostnames:
or yet another tunnel pointed at the ngrok tunnel server? The ngrok tunnel dashboard could be used for various development or debugging services but the dashboard itself will be exposed on the internet and might need to be protected as well.NGROK_AUTH
token with an ACL to attach to the custom Edge. You can add various Edge modules including Mutual TLS, IP restrictions, OIDC, SAML, and OAuth more and more!