Set Up Envoyer On An Existing Forge Site
So up until now you’ve been managing your Laravel project deployment with Laravel Forge, but are interested in moving to Envoyer.
“What happens to my existing setup?”
It’s actually very straight-forward to get your existing forge-git-hooked site to deploy out.
- Remove any pre-existing Forge deploy hooks that were set up on your git provider.
- Follow Taylor’s setup instructions on Laracasts. This should include setting up your deploy-on-commit hook, as well as the SSH key on Forge. Be sure to also set up your environment variables. Push your Envoyer project out when you’re ready.
- Update your site using Forge site configuration to point to:
/current/public
Example Configuration
4. SSH into your server and go to your project’s root.
5. Copy the content of your .env file: cat .env
6. Paste the .env content into Envoyer’s environment management interface and push it to production:
Environment Management in Envoyer
Envoyer actually just rides on top of your old files and adds what it needs. You might want to do some clean-up to get rid of the left-overs, but be aware that this might cause some down-time if things don’t go as expected. Be sure that you can afford some down-time to re-deploy, if anything should happen to go wrong.
The following command should remove all but the necessary files for you:
find . -maxdepth 1 -not -name “.” -not -name “current” -not -name “storage” -not -name “releases” -not -name “.env” -exec rm -rf {} ;
Your setup is preserved — just a bit of optional cleanup was all it took!