Release cadence
CLI to docs no release notes wa tsune ni update sare, version goto no compatibility note ga arimasu.
View release notesAnswer-first summary
Kono junban ga suisho desu: CLI install -> auth -> first tunnel, sono ato use case ni awasete MCP/webhooks/referrals. Nichijou unyou wa CLI Flags to Troubleshooting o tsukatte kudasai.
Quick command
instatunnel auth login -e you@example.com && instatunnel 3000 --subdomain docs-demoCommon failures and quick fixes
Compatibility, reliability, security posture no kakunin ni tsukatte kudasai.
CLI to docs no release notes wa tsune ni update sare, version goto no compatibility note ga arimasu.
View release notesSecurity whitepaper de policy enforcement, auth layer, operational safeguards o kakunin dekimasu.
Open security whitepaperTroubleshooting guide ni common failure, recovery step, CLI baseline ga matomatteimasu.
Read troubleshooting guidesConfigure InstaTunnel with config files and environment variables for persistent settings.
Create a global config file at ~/.instatunnel.yaml:
💡 Tip: Config file is automatically loaded if present in your home directory.
Use a custom config file location with the --config flag:
InstaTunnel automatically reads environment variables that match config keys:
🔒 Security: Never commit API keys to version control. Use environment variables for sensitive data.
InstaTunnel follows this configuration priority (highest priority first):
--api-key your_keyAPI_KEY=your_key~/.instatunnel.yaml| Option | Flag | Env Variable | Description |
|---|---|---|---|
api_key | --api-key | API_KEY | Your InstaTunnel API key |
server_url | --server | SERVER_URL | InstaTunnel server URL |
🎯 Best Practice: Store your API key in the config file (~/.instatunnel.yaml) or environment variable for convenience. Use command-line flags for temporary overrides.
Plan o mite, hitsuyo na toki ni guided start o tsukatte kudasai.
Pro/Business no MCP endpoint de wa tsugi o tsukatte kudasai: instatunnel 8787 --mcp.