Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I just purchased my first envoyer account and I had a question.
I have a new server provisioned in forge, and I have the default site.
I also want a development site on the same server, but I can't seem to figure out how to use different environment variables for just that server since Envoyer uses 1 .env file for the server itself and won't let you specify different ones for different sites.
Should I just use the environment manager in Forge for each site instead of a .env file?
You can use different environments for different servers.
PS: Using Forge may not be the best option, buying a server will be great. Because when you use Forge it's basically 10$ + DigitalOcean and if you don't follow "Forge + DigitalOcean". Better to have your own server. I recommend OVH.
Ok that I understand, when i'm deploying though, its not creating a symlink from the .env file in the root. The symlink for the storage folder is there though. Ive tried saving my env over and redeploying multiple times with no luck. Any ideas?
Also, I tried to create a migrate hook after dependency install, but I get undefined input artisan
I may just go back to forge by itself because it seems much easier.
I don't think so. You should email taylor though, and let him know your use case. Envoyer isn't very flexible right now, but he has been pretty helpful when I email questions/suggestions. I don't think it's meant to be a deployment server for anything other then production... for example you can't modify the composer install to install dev dependencies or anything.
I'm hoping over time Taylor will change it so he puts more of the power into the user's hands.
It's alright. I cancelled my envoyer account. I'm just going to use straight forge as i'm comfortable with it. Also, the zero downtime is great but sometimes I like to have full control by going into the server and doing what I have to do. It is a great product, it just might not be for me. Thanks for the help though.
Envoyer has a env link under server tab. You can copy paste your env file and save it.
Hooks must start with cd {{release}} then php artisan migrate --force.
With out cd into the release directory you will not have artisan command avalible.
@jekinney it doesn't answer the issue of different .env files for different servers under the same environment.
Please or to participate in this conversation.