Because any other VoIP application has an english name.
- As both client and server use code in
shared/
, the docker build context must be in root, otherwise it can't be used. Thereforedocker-compose
needs to be used, that can supply a different build context. - In root, call
docker-compose -f docker-compose-build.yml build
- Start individually
- Client:
docker run -e WEB_SOCKET_SERVER_URL=localhost:6503 -e 'ICE_SERVERS=[{\"urls\":\"stun:stunserver.org:3478\"}]' -d -p 80:80 funkgeraet_client
- Server:
docker run --rm -d -p 6503:6503 funkgeraet_server
- Client:
- Start with docker-compose
- Use template
docker-compose-build.yml
- Call
docker-compose -f docker-compose-build.yml up -d
- Use template
- Start individually
- Client:
docker run -e WEB_SOCKET_SERVER_URL=localhost:6503 -e 'ICE_SERVERS=[{\"urls\":\"stun:stunserver.org:3478\"}]' -d -p 80:80 ghcr.io/debugger-buam/funkgeraet_client
- Server:
docker run -d -p 6503:6503 ghcr.io/debugger-buam/funkgeraet_server
- Client:
- Start with docker-compose
- Use template
docker-compose.yml
- Call
docker-compose up -d
- Use template
- (optional) assign a fixed IP to your machines MAC via your routers DHCP
- In client/.env change
WEB_SOCKET_SERVER_URL
to use the IP of your development machine in your local network e.g. 10.0.0.2
- Install mkcert
- Install local CA root
mkcert -install
- Create certificates for the domains and IPs with which you want to access the app, e.g.
mkcert localhost 10.0.0.2
- Move those generated certificates into
./certs
and name themlocal.pem
andlocal-key.pem
- Move rootCA.pem onto phone (file location is in
mkcert -CAROOT
) - Security > Encryption & credentials > Install from storage
- Tested with Chrome (FF doesn't use root CA for some reason)
- Client:
npm run start-secure
- Server:
npm run start-secure