Laravel in GCP with Forge

As far as I know you can't at this point. Forge is focused on a VPS where you can host your application. However Google Cloud doesn't work like that exactly. In general you connect a domain to Google Cloud and they provide you with a server. However Forge is focused on having your own server.

You can deploy to GCP, but just not with Forge AFAIK.

This might help: https://cloud.google.com/community/tutorials/run-laravel-on-appengine-flexible

Well AWS has this feature & AWS is listed in forge. GCP also has similar compute engine where it provides VPS like instance. I am not interested in GCP App Engine. Can someone give me idea how to use compute engine for laravel.

@bobbybouwmann It is definitely possible to use Forge (and Envoyer) with GCP. I am using them both for production grade applications. The process is not as straightforward/simple as using one of the included server providers (i.e. AWS, Linode, DO). See below for some info.

@rajusutra Like I said above, the process is not entirely as straight forward as using one of Forge's server providers. The basic process is below:

1. Create a new Compute Engine instance to your specification. Wait for it to finish provisioning and copy the server's public IP.
2. Sign into Forge and click the Custom VPS option. Fill in the details from your Compute Engine instance from step 1. Note, you have to specify the RAM size.
3. Forge will give you a bash script/command to run on the server. This will provision the server with Forge's setup. Copy the ENTIRE script.
4. You need to SSH into the CE instance by one of two ways: 1) Use the GCP Console, or 2) Add a SSH key to the server and SSH in from your desktop terminal.
5. Paste the script from step 3 into the terminal and let it run. This will take some time as it installs the necessary software on your server. PHP, Nginx, etc.
6. As this process is working, you should see the server listed in your Forge dashboard and showing a "Provisioning.." status. There should also be some logs for your server, indicating what is happening on the server.
7. Once this process completes, you should be able to test the connection to your server through Forge and see "Successful."
8. To test that the web server and default site are live, copy and paste the server IP into your browser. You should see a PHP Info page.

A couple things to note here: if you did not enabled HTTPS support on the CE Instance, you must explicitly tell your browser to visit http:// or you wont see the site. This also does not cover setting up the database or any "real" sites. Additional work is needed for these to work, although the process for doing so is no different than if you used any other provider in Forge.

This is a pretty high-level overview that I provided just off the top of my head after doing this for several projects and lots of practice. Hopefully this gets you going and if not, I can provide additional resources that will help.

@bgweb Thanks for your reply. I will try it this week & surely inform you about the situation.

Wow thanks guys, Facing same challenge. now i wouldn't stress my self to create new discussion.

@bgweb Awesome! I didn't know that!

@rajusutra Have you had a chance to work through my suggestions? If it helped, please be sure to select my reply as the best answer. Thanks!

@bobbybouwmann Indeed, Forge is fairly flexible. You can basically connect it to any VPS you like. Obviously it is easier to use one of the pre-defined providers.

Hi @bgweb. I tried your suggestions but the script seems to end yet the server still shows as "provisioning" on forge. When i check the events it says: "Performing Forge Nginx Maintenance. Permission denied (publickey)." Any thoughts?