Ive been using Laravel and AWS for about a year now, i know there are people that deploy using code deploy (AWS) I have attempted doing it myself. But i want it to work with a load balancer and auto scaling group. Can anyone point me to a tutorial or give me a hand on this. I'm very grateful.
For working with AutoScaling Group, see: http://docs.aws.amazon.com/codedeploy/latest/userguide/auto-scaling-integ.html
For working with Load Balancer, see: http://docs.aws.amazon.com/codedeploy/latest/userguide/elastic-load-balancing-integ.html
Related
I would like to ask if it is possible to upload a laravel app to Google Cloud App Engine without using docker?
I tried to find any relevant resources but I can't find anything ob the internet that could help me wiith this. And if it is impossible, what should I do as my next step?
And if the only possible way is using docker, is it possible to add it after developing my laravel application?
I developed a desktop application in react and electronjs. And built an API with laravel, eveything works perfectly. The challenge I have is, how I can deploy and run my electron app locally without having to manually setup the laravel API.
I am looking for a way to have all of this setup and installed once. I checked out a couple of options and one of such is php-server but that wasn't still going to cut it.
Shell Scripting
I have thought about executing a shell script to create the server instance pull my laravel application from github, set it all up on docker.
The challenge is, if any of my users run docker ps they would see all the processes running on my docker instance.
A possible solution would be isolating docker so it's not accessible globally but only within the application.
I don't know how to achieve this.
If this is achievable please drop some guide on how to achieve that or maybe suggest a better way to handle my current situation.
I've spent 10+ hours yesterday reading up about / testing tutorials with google cloud and how I can use them as a host for my dynamic website.
With all of the new information in my head, I'm scrambled on what to do.
I already have my Virtual Machine Instance built with an IP that links to my domain, this works fine. However, I cannot for the life of me figure out how to put my project files on there. I figured it would have been something like "upload project files", "link with appengine", "link with cloud sql", but it seems like I was wrong?
In the tutorials, I uploaded googles sample projects (tutorials) by cloning a github link in the shell.
git clone https://github.com/GoogleCloudPlatform/getting-started-php.git
They also said a zip file could be extracted as an alternative.
Are those the only way of doing this? Should I create my own github and cone it in the shell?
Is it possible to link an AppEngine with a bucket that has my project files on there? (just throwing the question out there)
bonus question: once the files are uploaded, am I able to edit/develop through google cloud or do I need to edit changes in my files, then re-upload it to the cloud as an update?
This is my first time trying to have google (or any company) host my website, and this is completely foreign territory for me so any direction is much appreciated.
there are couple things mixed up in your question. Let me try to untangle them.
You don't need to create virtual machine if you want to run your PHP powered website on App Engine. There's a great overview in this article https://cloud.google.com/appengine/docs/standard/php/an-overview-of-app-engine
The way you run your PHP website on App Engine is by deploying your code to the version, you can do it using gcloud app deploy tool from your sources on your local machine. I recommend you to start by going through tutorial on here: https://cloud.google.com/appengine/docs/standard/php/quickstart
There's currently no way to link Google Cloud Storage bucket with App Engine version, you have to deploy your code yourself using either gloud app deploy or using App Engine Admin API that gcloud is using internally.
There's no way to edit your App Engine application code in the cloud.
I am currently learning frameworks in php. I decided to try laravel.
i have tried its installation and routing example. while next step it says homestead installation instructions over there. It looks like any virtual machine to be installed . homestead description link
I want to know is it compulsory laravel should be use with homestead?
if i don't use is there any effects on my code efficiency or performance?
Homestead is not compulsory. You can run Laravel with any common web server as long as you hit the proper requirements.
But Homestead does greatly ease the difficulty of having to setup a development environment, and it also lets you closely mimic your production server as to make the whole Download->Develop->Deploy process seamless.
Laravel Forge is a service that lets you manage your servers and set them up in such a way that almost mirrors Homestead. To See more, Go to the Laravel Forge Homepage
We're putting together a PHP site that we plan on deploying to Elastic Beanstalk, and I'd like to create a virtualized dev environment to match production. I've got a few questions about it, though.
So it looks like I can use vagrant-aws and feed it a custom AMI - presumably one that would be created by Beanstalk. Will this actually work, though? It seems like it uses rsync to copy any new files up. Is that going to slow down development as I wait for it to sync up?
More importantly, it seems like this relies on a network connection if you want to do any development. Is it possible to take it offline so I can develop without a connection (e.g. on a plane, on a bus, etc.)?
As an alternative, has anyone put together a Vagrantfile that matches the packages and setup of Elastic Beanstalk? I couldn't find anything in my searches, but maybe I was looking in the wrong spot?
Finally, are there any recommendations for pulling off this sort of dev testing? Am I thinking about this the right way, or is there a better way to do this?
I'd say that the cleanest way is to use a tool like Packer to create an image for both EC2 and Vagrant. That way you control the image you're using and you know it's the same for both EC2 and Vagrant.
Elastic Beanstalk can be handed a custom AMI and if your devs have the vagrant box downloaded they can work when disconnected.
It's not the easiest option since you have to configure all the packages on the image yourself but it's a good way to keep your dev boxes and production boxes in sync.