my prefect server setup prefect-metrics.waow.tech
python orchestration
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

fix pull step: set UV_PROJECT_ENVIRONMENT=.venv

unset VIRTUAL_ENV isn't enough — uv also reads sys.prefix which is
/usr/local in the prefect image. UV_PROJECT_ENVIRONMENT explicitly
tells uv where to create the project venv.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

zzstoatzz b4f6f47b 6fef3447

+1 -1
+1 -1
prefect.yaml
··· 3 3 pull: 4 4 - prefect.deployments.steps.run_shell_script: 5 5 script: | 6 - bash -c "rm -rf my-prefect-server && (git clone --depth 1 --branch main https://tangled.sh/zzstoatzz.io/my-prefect-server.git my-prefect-server || git clone --depth 1 --branch main https://github.com/zzstoatzz/my-prefect-server.git my-prefect-server) && cd my-prefect-server && pip install -q -U uv && export PATH=\"$HOME/.local/bin:$PATH\" && unset VIRTUAL_ENV && uv python install 3.14 && uv sync --python 3.14" 6 + bash -c "rm -rf my-prefect-server && (git clone --depth 1 --branch main https://tangled.sh/zzstoatzz.io/my-prefect-server.git my-prefect-server || git clone --depth 1 --branch main https://github.com/zzstoatzz/my-prefect-server.git my-prefect-server) && cd my-prefect-server && pip install -q -U uv && export PATH=\"$HOME/.local/bin:$PATH\" UV_PROJECT_ENVIRONMENT=.venv && uv python install 3.14 && uv sync --python 3.14" 7 7 - prefect.deployments.steps.set_working_directory: 8 8 directory: my-prefect-server 9 9