If you make your migrations right it's doable. You can run old code on a migrated DB if the migrations are only additive, and you haven't changed or deleted something the old code relies on.
Then you can just do one server at a time like this:
- Take Server 1 Offline
- Update Server 1
- Use Server 1 to perform DB migrations
- Bring Server 1 Back Online
- Take Server 2 Offline
- Update Server 2
- Bring Server 2 back online
Or just use Envoyer. The other question is do you really "need" zero downtime deploys or does it just sound nice to have? Forge can deploy one of my apps in less than 30 seconds.
Last updated
by
@james4645
2 years ago.
ibiza385 liked this reply
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast