Store MariaDB and media data on the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media) instead of Docker named volumes, so they live on the big disk and survive 'down -v'. Drop the host 'make check' from the deploy job: the image builds already run tsc for every workspace, so no Node toolchain is needed on the runner.
Store MariaDB and media data on the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media) instead of Docker named volumes, so they live on the big disk and survive 'down -v'. Drop the host 'make check' from the deploy job: the image builds already run tsc for every workspace, so no Node toolchain is needed on the runner.
Store MariaDB and media data on the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media) instead of Docker named volumes, so they live on the big disk and survive 'down -v'. Drop the host 'make check' from the deploy job: the image builds already run tsc for every workspace, so no Node toolchain is needed on the runner.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Store MariaDB and media data on the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media) instead of Docker named volumes, so they live on the big disk and survive 'down -v'. Drop the host 'make check' from the deploy job: the image builds already run tsc for every workspace, so no Node toolchain is needed on the runner.
LGTM