Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions scripts/set-test-tokens.sh
Original file line number Diff line number Diff line change
Expand Up @@ -53,12 +53,14 @@ if [[ $# -ne 0 ]]; then
_fail "this script is hard-coded and does not accept arguments" 2
fi

LIVEKIT_API_KEY="devkey"
LIVEKIT_API_SECRET="secret"
LIVEKIT_API_KEY="${LIVEKIT_API_KEY:-devkey}"
LIVEKIT_API_SECRET="${LIVEKIT_API_SECRET:-secret}"
LIVEKIT_URL="${LIVEKIT_URL:-ws://localhost:7880}"
LIVEKIT_VALID_FOR="99999h"
LIVEKIT_URL="ws://localhost:7880"
_grant_json='{"canPublish":true,"canSubscribe":true,"canPublishData":true}'

echo "set_test_tokens: Using LIVEKIT_URL: $LIVEKIT_URL" >&2

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Can we avoid printing here? We have plenty of logs across SDK layers/end products (ROS Portal) that log which URL is being connected to. I also run individual tests often and call into this script first, so I'll be getting more output

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need some log to indicate the creds being used so we can prevent devs from using the wrong creds. I could change it to "using local server" or "using cloud server" ?


if ! command -v lk >/dev/null 2>&1; then
_fail "'lk' CLI not found. Install: https://docs.livekit.io/home/cli/" 2
fi
Expand Down
Loading