zeabur-migration

Your Zeabur deployment gets stuck waiting for database migrations because the application expects a separate migration service that is not configured. It remains in a perpetual wait state until you integrate migrations into the API startup command or set up a dedicated migrator service.

To fix a Zeabur service stuck on database migrations, you can either modify the API service's startup command to include migration execution or configure a separate dedicated migrator service. Both methods resolve the indefinite wait state.

Running database migrations on API startup is simpler for smaller applications, while configuring a separate migrator service in Zeabur is better when your app expects migrations to run independently. Your choice depends on your deployment architecture.

Yes, this solution works for Docker deployments on Zeabur experiencing deployment troubleshooting issues. It diagnoses services stuck in a perpetual migration wait state and provides solutions by modifying the API command or configuring a separate migrator service.

When Zeabur database migration is not working, you should diagnose if the service is stuck in a perpetual migration wait state. Resolve it by modifying the API service's command to include migration execution on startup or by configuring a separate migrator service.