Deploying on Azure / Boot Order
Hi! 
I'm deploying Twenty CRM v1.4.1 with separate server and worker containers on Azure
and need help understanding the startup sequence.
My questions:
1. What's the correct startup order? Should the server container fully start before
launching the worker, or can they start simultaneously?
2. Database initialization - Does the server need to complete all migrations and
table creation before the worker can connect? Or can the worker handle waiting for
missing tables?
3. What happens if the worker starts first? I'm seeing boot loops where containers
restart - is this because the worker tries to access tables that don't exist yet?
4. Any specific startup dependencies I should be aware of between server and worker
containers?
I'm deploying Twenty CRM v1.4.1 with separate server and worker containers on Azureand need help understanding the startup sequence.
My questions:
1. What's the correct startup order? Should the server container fully start before
launching the worker, or can they start simultaneously?
2. Database initialization - Does the server need to complete all migrations and
table creation before the worker can connect? Or can the worker handle waiting for
missing tables?
3. What happens if the worker starts first? I'm seeing boot loops where containers
restart - is this because the worker tries to access tables that don't exist yet?
4. Any specific startup dependencies I should be aware of between server and worker
containers?
