Skip to Content
šŸŽ‰ TestoQA 1.0 is released
DocumentationUpdatingLocal Docker Setup

Updating TestoQA (Docker Setup)

This guide explains how to update an existing local Docker setup of TestoQA when:

  • The repository code has changed
  • Docker images have been updated
  • The Docker Compose configuration has changed

The steps below are safe for local try-out and preserve your database unless explicitly stated otherwise.

Prepare (run before pulling changes)

Before updating TestoQA, make sure you are in the correct project directory and that any existing containers are stopped. This avoids conflicts during the update process.


1) Ensure you are in the TestoQA project root

Confirm that you are in the TestoQA repository root (where Docker files live):

pwd ls docker-compose.yml

If the file is missing, change into the project directory:

cd /path/to/TestoQA

2) Stop running containers (choose based on whether you want to keep data)

Choose one of the following options.

Stop the application and reset containers without deleting the database or uploaded files.

docker compose down

Use this in almost all cases when updating TestoQA.


Start completely fresh (deletes data)

Stop the application and permanently deletes all stored data.

docker compose down -v

āš ļø Warning

This removes:

  • The PostgreSQL database
  • Uploaded files
  • All other persisted data

Use this only if you intentionally want a clean slate.

Pull the latest source code

Always start by updating your local repository:

git pull

If TestoQA uses prebuilt images (for example, :latest from a registry), pull the newest versions:

docker compose pull

This fetches the latest images for all services defined in your docker-compose.yml.

Force container recreation (safe fallback)

If Docker does not detect changes but behavior seems outdated:

docker compose up --force-recreate

Docker will reuse volumes (including PostgreSQL data) automatically.

Run database migrations (if required)

If the update includes new database migrations, apply them:

docker compose run --rm testoqa-tooling prisma migrate deploy
Note

This step is only required when the update introduces schema changes.

Follow Setup Guide

After updating, refer to the step 5 to last of initial setup guide for any additional steps or configurations needed.


Optional: Cleaning Up Old Docker Resources

Over time, unused images may accumulate on your system.

Remove unused images safely:

docker image prune

Aggressive cleanup (removes unused containers, networks, and images):

docker system prune
Warning

Aggressive pruning may remove resources used by other Docker projects.

Last updated on