Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Chris1904's avatar

How to best utilize Envoyer using a multi server setup?

Hi there,

I am trying to grasp the concept still fully.

So, I have a server setup similar to this:

  • load balancer server
  • x amount of application servers
  • worker server
  • database server

Not that it matters, but the servers are all Forge provisioned, inspired by https://serversforhackers.com/scaling-laravel

Should Envoyer only deploy the application servers? Or should it deploy all the servers? Are there any possible negative outcomes having it deploy all the servers?

Being a novice when it comes to scaling and deployments, I would appreciate any feedback and personal experiences :-)

Best, Chris

0 likes
1 reply
ejdelmonico's avatar

Your issue is one of either preference or necessity. There is no easy way to estimate your needs because only you have total grasp of the issue. As far as preferences, I would use separate repos for the application and worker code and deploy them with Envoyer. I don't feel that Envoyer is the correct tool for the DB server and the load balancer is just config. The only reason to use Envoyer with Forge is to not have interruption in service/access. Envoyer allows for many processes to run during deployment like stopping workers and restarting or route caching whatever.

Additionally, I would like to mention that many people confuse Envoyer the service with Envoy. Envoy is a task templating system that works great with server deployment tasks.

https://cl.ly/pvC9

For more information on Envoy, go to https://serversforhackers.com

Please or to participate in this conversation.