Level 1
Forge doesn't use your SSH key to deploy, it adds its own to your server. Have you ever had a successful deployment with Forge?
Aug 21, 2015
5
Level 2
Problem connecting to my Server from Laravel Forge to DigitalOcean
Hi,
Anyone had problems with the deployment on Laravel Forge?
it gives me the following error:
We were unable to deploy your project to your server.
Also, the time to provisioning my DigitalOcean within Forge was aproximately 7 min.
The error that it gives me is related with the SSH key that I copy from my computer to connect to the server. The same that I used on DigitalOcean.
Thanks for advanced.
Level 2
Thanks for your reply @jbrooksuk, yes and I received one email to my email account from Bitbucket with another SSH Key to connect to my repositories.
Is needed to add to Forge that key?
Level 1
In which case Forge should already have added your SSH key for you - it does so for me. Have you since changed id_rsa or id_rsa.pub manually on your server?
Level 2
It doesn't added the key for me, only created one when I use bitbucket to add the repository (different from the id_rsa that I created to connect to my Digital Ocean servers).
Seems to be the env variables used to connect to the forge@servername database.
If I have working inside my dev machine, how can I configure environment variables to production?
Level 2
Yeah, when you edit your .env vars within Forge you can deploy fine.
I copy all my .env vars to the Forge .env file but something I don't understand, why is used APP_ENV=local as well in the Forge environment and it does work?
Please or to participate in this conversation.