scripts/playwright-webserver-command.sh

#!/bin/sh
if [ -n "$USE_DOCKER" ]; then
    set -ex
    yarn build --mode development
    docker build -t element-call:testing .
    exec docker run --rm --name element-call-testing -p 8080:8080 -v ./config/config.devenv.json:/app/config.json:ro,Z element-call:testing
else
    cp config/config.devenv.json public/config.json
    exec yarn dev
fi
Build Docker image on slim base (#3204) * Build Docker image on slim base * Run Playwright tests against Docker container For Playwright end-to-end tests in CI, instead of running a development webserver with `yarn dev`, build and deploy a Docker container for Element Call and use that as the webserver to test against. * Shut down playwright webserver gracefully When using a containerized webserver, this stops the container once tests finish. * Increase Playwright timeout in CI --------- Co-authored-by: fkwp <github-fkwp@w4ve.de> 2025-06-06 12:04:57 -04:00			`#!/bin/sh`
			`if [ -n "$USE_DOCKER" ]; then`
			`set -ex`
run playwright in dev mode 2026-01-09 14:41:07 +01:00			`yarn build --mode development`
Build Docker image on slim base (#3204) * Build Docker image on slim base * Run Playwright tests against Docker container For Playwright end-to-end tests in CI, instead of running a development webserver with `yarn dev`, build and deploy a Docker container for Element Call and use that as the webserver to test against. * Shut down playwright webserver gracefully When using a containerized webserver, this stops the container once tests finish. * Increase Playwright timeout in CI --------- Co-authored-by: fkwp <github-fkwp@w4ve.de> 2025-06-06 12:04:57 -04:00			`docker build -t element-call:testing .`
			`exec docker run --rm --name element-call-testing -p 8080:8080 -v ./config/config.devenv.json:/app/config.json:ro,Z element-call:testing`
			`else`
			`cp config/config.devenv.json public/config.json`
			`exec yarn dev`
			`fi`