Skip to content

Latest commit

 

History

History
71 lines (60 loc) · 1.89 KB

docker-project-specific-commands.md

File metadata and controls

71 lines (60 loc) · 1.89 KB

← Back: Documentation Overview

Useful project specific Docker actions

Frontend

All commands have to be run inside a shell in a container.

docker compose exec frontend bash
#Command to open the frontend container in a shell

🐳To escape the container:

exit

🐳Biome check

yarn biome:check
#runs Biome, like in GitHub Actions pipeline, but in Docker

🐳Stylelint check

yarn run stylelint:check
#runs stylelint, like in GitHub Actions pipeline, but in Docker

🐳TypeScript Compiler check

yarn run tsc:check
#runs TypeScript Compiler check, like in GitHub Actions pipeline, but in Docker

Backend

All commands have to be run inside a shell in a container.

docker compose exec backend bash
#Command to open container in a shell

Aliases

🐳The migrate alias will apply any pending database migrations to update the database schema according to the changes defined in Django.

migrate
#equal to "poetry run python /app/manage.py migrate"

🐳When you run the makemigrations alias Django will create database migration files based on any changes to your project's models.

makemigrations
#equal to "poetry run python /app/manage.py makemigrations"

🐳The seed alias will seed the local database with dummy data. Further docs here: Seeding.

seed
#equal to "poetry run python /app/manage.py seed"

🐳The collectstatic alias will collect and copy the static files from Django apps into the appropriate location as configured in the Django project's settings.

collectstatic
#equal to "poetry run python /app/manage.py collectstatic --noinput"

🐳The pipeline alias will run the backend GitHub Actions pipeline in Docker.

pipeline
#equal to "poetry run /app/run-pipeline.sh"