trent-local-voice-server-prod_skill

Overview

This skill deploys a local production-mode voice development environment using ngrok for outbound calling. It orchestrates ngrok, a voice server, backend, and frontend in a tmux layout so you can test voice flows from your local machine. Use it to quickly expose the voice server to the internet and run the full stack together for debugging and manual tests.

How this skill works

The script creates four new tmux panes and starts ngrok to expose port 8080. It reads the ngrok public URL, injects that as VOICE_OUTBOUND_BASE_URL, then launches the voice server on port 8080, backend on 8000, and frontend on 3000. The process uses environment variables for prod mode and retries to fetch the ngrok URL before failing.

When to use it

• You need to test outbound voice calls from your local development environment.
• You want a reproducible tmux layout that runs ngrok, voice server, backend, and frontend together.
• You need to debug voice call flows that require an externally reachable callback URL.
• You want to run the full stack locally in production mode for QA or demo purposes.

Best practices

• Install and authenticate ngrok, run tmux, and install jq before using the script.
• Use a paid ngrok plan or reserved domain if you need a stable public URL across sessions.
• Keep sensitive credentials out of logs and environment variables when sharing output.
• Run the script from the repository root so relative frontend path resolution (cd frontend) works.
• If ngrok URL fetch fails, open the ngrok web UI at http://localhost:4040 to inspect tunnels.

Example use cases

• Start the local voice environment to confirm outbound call routing and audio playback.
• Quickly reproduce a voice-related bug by running the exact prod-mode services locally.
• Demo voice agent interactions to stakeholders using the local frontend and ngrok tunnel.
• Develop and test integration logic that depends on the voice server's outbound callbacks.