Docker Dev Services Restart

To restart Docker development services safely after a system reboot, execute the provided scripts from your project root to initialize PostgreSQL and ElectricSQL in the correct order, preventing data loss and verifying service health.

Yes, you can perform a targeted service restart for ElectricSQL independently. This allows you to resolve misbehaving ElectricSQL instances without affecting other running components like the PostgreSQL database.

The safest way to apply configuration updates from docker-compose.dev.yml is using the Skill's safe configuration update procedures, which facilitate restarting services with new settings while actively minimizing data loss risks.

You can verify the health of ElectricSQL and Shape APIs after restarting Docker containers by running the included verification commands, which check the operational status of Docker containers and API availability.

To recover database data using SQL scripts after accidental loss during a Docker restart, follow the outlined data recovery procedures, which provide specific SQL commands to restore PostgreSQL data.

Restarting Docker development services risks data integrity due to improper shutdown sequences or configuration mismatches. This Skill prevents data loss by providing correct restart ordering, targeted recovery commands, and health verification.