microscopic-dress-75199
09/22/2025, 4:46 AMtall-airline-16756
09/22/2025, 4:46 AMtall-airline-16756
09/22/2025, 4:47 AMmicroscopic-dress-75199
09/22/2025, 4:49 AMmicroscopic-dress-75199
09/22/2025, 4:49 AMtall-airline-16756
09/22/2025, 4:49 AMlivekit-server --dev), the default API key is devkey and the default API secret is secret. These defaults are set up automatically to make local testing easier for you. If you have any questions or need help with this, feel free to ask!tall-airline-16756
09/22/2025, 4:49 AMlivekit-server --dev), it conveniently uses default credentials for you:
• API Key: devkey
• API Secret: secret
These defaults are perfect for local testing, so you don’t have to worry about setting them manually right now.
2. For Dependent Services (e.g., SIP, Egress, Ingress)
If you want to configure the API key and secret for services like SIP, Egress, or Ingress, you have two friendly options: using a configuration file or environment variables. Let’s explore both!
Using a Configuration File
api_key: your-api-key
api_secret: your-api-secret
ws_url: <ws://host.docker.internal:7880> # or the appropriate IP for Linux
redis:
address: host.docker.internal:6379 # or the appropriate IP for Linux
Simply mount this file into your container when you run it. For example:
docker run --rm \
-e EGRESS_CONFIG_FILE=/out/config.yaml \
-v ~/livekit-egress:/out \
livekit/egress
Using Environment Variables
If you prefer, you can set the API key and secret directly as environment variables like this:
docker run --rm \
-e LIVEKIT_API_KEY=your-api-key \
-e LIVEKIT_API_SECRET=your-api-secret \
-e LIVEKIT_WS_URL=<ws://host.docker.internal:7880> \
livekit/egress
Just swap out your-api-key and your-api-secret with the credentials you want to use.
3. For Production
When you’re ready to move to production, I recommend checking out the LiveKit deployment guides. They’ll help you manage your credentials securely and smoothly.
If you have any questions or need further help, feel free to ask. I’m here to support you every step of the way!
Sources: Running LiveKit locally | LiveKit Docs | Self-hosting the Egress Service | LiveKit Docs | Self-hosting the Ingress Service | LiveKit Docs | README.md