https://github.com/itsmebriand/livekit-svelte-exploration
A simple voip application built with SvelteKit, LiveKit, and TailwindCSS
https://github.com/itsmebriand/livekit-svelte-exploration
livekit node svelte sveltekit tailwindcss typescript
Last synced: 5 months ago
JSON representation
A simple voip application built with SvelteKit, LiveKit, and TailwindCSS
- Host: GitHub
- URL: https://github.com/itsmebriand/livekit-svelte-exploration
- Owner: ItsMeBrianD
- Created: 2021-07-17T16:30:37.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2021-07-18T02:58:04.000Z (about 4 years ago)
- Last Synced: 2025-04-02T20:44:48.419Z (6 months ago)
- Topics: livekit, node, svelte, sveltekit, tailwindcss, typescript
- Language: Svelte
- Homepage:
- Size: 61.5 KB
- Stars: 9
- Watchers: 2
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Livekit + Svelte = 🦾
This repo contains a small VOIP application built using [SvelteKit](https://kit.svelte.dev), [LiveKit](https://livekit.io) and [TailwindCSS](https://tailwindcss.com).
To get it set up, you only need to do a few short setup steps.
1. Place the ip for the host you are running on into [`docker-compose.yml`](./docker-compose.yml) and [`config.json`](./src/config.json)
- (Hint: it goes in the `command` property for the `sfu` `service`)
1. Generate an access token / secret pair
1. At time of writing, this can be done with the following command:
`docker run --rm livekit/livekit-server generate-keys`
1. Place your access token into `/secret/lk_access_token`
1. Place your secret key into `/secret/lk_access_key`
1. Place both into `/server-config.yml` as a key value pair for `keys` (i.e. `access_token: secret_key`)
1. Run `docker-compose up`, and connect to the instance at [localhost:3000](localhost:3000)
- If you are going to be changing the svelte code, you can use `docker-compose up sfu` and `npm run dev` to start the sfu in docker, and the frontend in dev mode.
1. If you are going to be connecting to a local instance (i.e. from one machine to another via LAN), you will need to configure your browser to allow [the browser to access your microphone and camera](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia) on a *specific* insecure host. For Google Chrome, you can do so with [this](brave://flags/#unsafely-treat-insecure-origin-as-secure) flag (it should look like `http://x.x.x.x:3000`). To read more about why this step is needed, the chromium project has a good writeup on why they made the restriction [here](https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins).