I've tried to talk about it on this channel, and numbers show that those videos were not that popular. I guess CI/CD are relevant only for like 5-10% of Laravel developers who have projects suitable for it.
@@LaravelDaily well yes, more advanced stuff applies to lower numbers same as there is less mid/senior developers. But it would be beneficial to laravel developer community in general, as there is hard to find any advanced info, whole youtube is full of junior level videos.
Thank you for making this video. This is showing the current real world seanario. Speacially the shared hosting stuffs. Not all companies or person can afford vps ones or sometimes can't even get the privilege to purchase. In my country it is hard to get international items to purchase. Hope this will help others. Thanks again.
Thanks so much. Fantastic video as all of yours are. I'm a retired IT guy doing Laravel as a hobby really. Fascinating to compare my journey with your gang!
Forge provisions servers for you .. but will it keep them up to date over time & patch issues that arise or is it hands-off after the initial provisioning? Or say a new version of PHP is released. Does Forge go install it on all your servers automatically?
I use PHPloy to deploy the changes. Although it is manual, the good thing is it only deploys changes based on files changed in commit files in Git, so I don't need to deploy the whole app or remember which files are changed and should be deployed. So if the deployed version in your server is on commit 1 while your local is on commit 3, it will only deploy changes in commit 2 and 3. What's good about this is, if it's really really necessary, you can basically log in to your production server and change stuff quickly (for example to fix a very simple but very bad typo or some critical bugs) rather than having to go through the whole "make changes, git add, git commit, merge to master branch, then phploy" process. I once tried both the manually git push from local then git pull from live (or setup an automated git hooks), but when I tried to do a production change above, it ends up making the repo in the production server having a staged git changes, making the future git pulls fail because there is an ongoing change not yet committed. I could manually git add then push in production then pull the changes to my local, but it ends up being a hassle. Haven't really explored the envoyer (deploy to a release folder, then symlink the live version to that release folder) thing, because it seems to require quite a major change (since it requires storage and upload folders to be tweaked to survive changes between releases) and if the changes to be deployed is only a fix on typo in one file, it seems a bit overkill to deploy a whole release containing the whole app? I get that the advantages is we can roll back to previous releases quickly, but I find it easier to fix the breaking bugs quickly then deploying the necessary updates in the near future. Of course this method works because I work in a quite a small team (< 5 developers), I'm sure it doesn't scale in bigger teams with more complicated deployment processes.
One killer option for me on the shared Hosting, I just learned that Laravel's/Filament database notifications doesn't work on Shared Hosting, only on VPS. To just test the functionnaloity, you need to queue:listen command in the terminal and stay there. So it's a killer function that shared hosting doesn't have.
Thank you, but I've got a question. Why no any info about compiling js&css with nodejs for frontend? How do you handle it on server? Is it possible to run compiling process on forge?
Thanks for this video. I use Google App Engine (serverless) Standard with Google Cloud SQL for laravel. It is very simple to setup, scale and deploy. I am surprised this is not used as often.
Laravel is a failure considering this survey. Shared hosting? No git? That s a disaster. Laravel is not for cheap projects. Don't use it, better use something else...
Clearly one of the best explanations on the topic. I think that, specially for juniors it is a headache when you start deploying your project, as there are many ways to do so. I'm personally moving from Shared Hosting to DigitalOcean, to avoid headaches from setting a laravel project on a Shared Hosting
I guess all the survey has a "bias": all answers stems from the background everyone has. Nonetheless, the video is very informative. Even if I have a Mac OSX system available, for instance, I prefer to develop Laravel Apps on a Debian machine configured with specs that are very similar, if not identical, to the intended production server (VPS and/or Dedicated Server) with a "git" workflow. Debian has a very stable LTS branch (the best, I should say, and this is because many Linux distros are derived from Debian). That guarantees no hassle while developing/deploying and during the maintenance phase. Sometimes by writing simple scripts you can recreate a similar workflow to Forge or other excellent services around. Of course, that means you need to have intermediate skills to manage a server that is not the case for many developers. I like having perfect control of the production server...especially nowadays where you can find cheap and scalable VPS.
Thanks for this interesting video. I use Laravel Vapor and was surprised it didn't come up more. I hate server administration stuff and find Git a little difficult, and I like the auto-scaling, so this was a great option for me. I will have to see how the costs are in the long run, though, and whether it's the best option for all my sites.
Finally, someone agrees with me on Laravel Forge's Automatic Deployment is rather risky for a production server. Personally, I've never used it. Always have my Forge open in a browser tab. Doesn't take me 5 seconds to push deploy. I'd just rather not have some code I merged but haven't tested, go up to the live server.
Create two branches one for production and another one for staging. From your computer you push to staging and after confirming that everything is ok you merge to production and your live server will update without any risk ;)
2 or 3 people mentioned Azure, not enough to make it to the stats. I guess it's not a "standard" environment for Laravel and needs extra configuration to make it work.
Hi, I don't recommend shared hosting for any Laravel project, especially with Vue. My recommendations: laraveldaily.com/what-server-is-needed-to-deploy-laravel-projects/
@@igbokwelaurence5882 Its paid service that manages your server. It works great for setting up Laravel apps. You can choose from multiple vps providers including linode or digital ocean.
it is really interesting topic. with laravel deployment you always need vps to use laravel features like queues (redis) which you cannot get on most of shared hosts. there pros and cons for both hosts. with vps i faced 1 issue how to setup emails send and receive this was the reason i moved to shared host where email server is already setup you are receiving and sending emails with ease. i am using shared host with ssh and gitlab to deploy my laravel projects but there were some issues like no composer installed, older version of PHP cli (5.4) which will not allow you install composer and latest versions of laravel. fond solution to install composer on shared host. with help of .bashrc and .bash_profile able to update php cli version and composer command available to run composer and install latest version of laravel. But you cannot install redis or other os packages on shared host. still looking for a solution for VPS with email server up and running to receive emails.
I have git and Plesk on my VPS. There is sometimes pain in the butt, since Plesk only supports single SSH key for Git repository and I have to create a new one and add it to ssh agent every time I use git pull. But, yeah - git and ssh is the case
I sometimes use CI/CD with git for deployment on shared hosting, then I use ssh to create symbolic link and also to migrate, I also do add migration routes to the super admin group.
Tip for the next survey. Use more checkboxes, radio buttons and select boxes, and less textareas. It will definitely help with summarising and visualising the data.
As it mentioned Laravel Forge with Digital Ocean is $22/month. Shared hosting can be 10 times cheaper and easier to operate for beginners - this makes sense for small projects.
Hey very nice to see. On note here: I am working in market research (yes, powered by laravel :)) and I would recommend, for any upcoming surveys, to use options instead of open answers. Not only is it easier for you to gather the answers, but it will also result in a much higher participation rate. Just my 2 cents and thank you for your work. My team learned a lot from your channel!
Shared hosting + git ?? That's interesting, though I understand it can be unsafe and I can't imagine managing Laravel migrations.. might be a pain at the end. Im surprised no one mentioned Heroku. It's free, you can use a domain name (have to register a credit or debit card) pricing starts at 5 which is very similar to those mentioned in the video, I do not own a paid account but often times I've been tempted to pay for one, the deployment is easy as pie too once you have everything configured. Nice video!
Its much simpler than you think. I also use the git function on my cPanel to deploy projects and there is a button that pulls your changes from git. cPanel connects to github for example through ssh by generating an ssh key which you add to your git repo so a secure connection is established. There is also a Terminal in cPanel that I use to run composer and artisan commands if I don't want to use an ssh client. Then finally the CRON manager for task scheduling.
@@MrError-ml3lz I have the free plan. I think if you're anything like me, a novice Laravel developer and want to start deploying you should consider that service, it's easier than shared hosting + it is free. However as @mensah felix replied, shared hosting might have it's advantages, I just haven't deployed any websites with shared hosting + git.
I use Bluehost for all of my projects. I only pay 15$ per month and I get pre configured server with ssh, git. and with one account I can host ‘unlimited’ projects with ‘unlimited’ storage & email. I have 2 accounts with about 6 projects each and everything is working fine. No problem, no slowing down and deploying using git. Mind you tho, all my projects have relatively low traffic
Hello, Im currently using Laravel Forge to deploy my applications on AWS, however i cannot find where the databases are stored. I have looked under RDS and the other server options, however i cannot find it. Do you happen to know where the databases are stored when you deploy to AWS through forge? Thanks
Thanks very much for this video, very useful :). I have a question, I am currently working on a quite big project using laravel with jetstream+inertia and I was thinking of deploying maybe with digital ocean or Google cloud service , laravel forge is the best way to do it? Could you orient me into what I should look into to study please Thank you
You don't know until you TRY. No one can tell you what is the best for YOUR scenario. But I do advise Forge + Digital Ocean as the *easiest* entry level.
If you use forge, can you have more than one laravel app per forge-managed server? Or is it one server per laravel app? Because if you can have multiple, let's say 2-3, low traffic sites per server, the cost is not very high i think.
We primarily use Jenkins to pull, build, test via docker etc then SCP artifacts to destination (mainly for removing link to git on application servers), rebuild and symlink live. A nice way of ensuring we never mutate or destroy old deployments. There was a great tutorial done during a past laracon on using Jenkins with laravel for anyone wanting to learn more
Shared hosting actually shocked me also. I have run a quick app before on a reseller package but sometimes server resources are just not great on them. I now use Ionos VPS as they offer great deals and half price for 6 months most of the time.
I was using WebFaction for almost a decade but when it shut down (was bought by GoDaddy) I migrated all of my sites to OpalStack. Yes, I've choose shared hosting option, but as WbFaction did have, I comes with SSH, Git, and almost all of the stuff I need for smaller projects. So far I am very satisfied and I can recommend it to everyone who needs a decent shared hosting plan.
@@insurg3nt3 It is simple. You need a git (I use BitBucket because it was free when I started and I am a bit lazy to transfer everything to another service). Then it is just a matter of enabling git in your project, commit and push changes to BitBucket. Then I SSH to OpalStack, into my project and simply git pull everything from BitBucket. This last step was one which I am hoping Povilas will go a bit deeper in one of his next videos. OpalStack has a good tutorial on how to start Laravel app on their shared hosting.
@@LaravelDaily yeah sail is not popular but docker is very popular also very important when it comes to deployment like load balance and more and also for team based project, maybe can you ask people's if it is worth making video like make a vote on Twitter if you get many votes maybe then do a video 🙄
In small projects it's better to use Codeigniter or other framework who doesn't rely on terminal, but thinking again ssh/terminal access is needed when need implement extra features.
Sir: I follow your all videos . but if you find a time plz make social network series I search in youtube but not find a good series but ur way of teaching I understand ur teaching technique. in social network all problem will cover that everyone have ...
Sorry, for now I'm not planning such series. For a *proper* social network, it would be a full course with huge length, like 5+ hours. I don't have that much time available, sorry, focused on other topics now.
I ssh into server, git pull, then create a copy of the git folder, run composer install and other stuff, then change symlink. If using php-fpm at this point you need to restart php-fpm. After confirming it worked i delete old folder the symlink used to point to
This video is Gold. This is how should a community work. Thank you for this.
Would like so see more info for advanced users. Like proper CI/CD, how to tests things before production and so on...
I've tried to talk about it on this channel, and numbers show that those videos were not that popular. I guess CI/CD are relevant only for like 5-10% of Laravel developers who have projects suitable for it.
@@LaravelDaily I would love to see a CI/CD deployment video.
@@LaravelDaily well yes, more advanced stuff applies to lower numbers same as there is less mid/senior developers. But it would be beneficial to laravel developer community in general, as there is hard to find any advanced info, whole youtube is full of junior level videos.
I agree. I'm currently doing CI/CD for staging environments. via Github Actions & AWS.
Github action works well for this, run your tests suite on pushing to GitHub
thanks
we need video explain best way to deploy Laravel on digital ocean
I have done a few videos on it already: as mentioned in this video, I recommend Laravel Forge for doing it.
Thank you for making this video. This is showing the current real world seanario. Speacially the shared hosting stuffs. Not all companies or person can afford vps ones or sometimes can't even get the privilege to purchase. In my country it is hard to get international items to purchase.
Hope this will help others.
Thanks again.
want to see a video using a simple laravel app with github action and digitalocean.
Thanks so much. Fantastic video as all of yours are. I'm a retired IT guy doing Laravel as a hobby really. Fascinating to compare my journey with your gang!
I was thinking i am the only one who use zip and unzip, but great to know all, you are really doing a great job 👍
Forge provisions servers for you .. but will it keep them up to date over time & patch issues that arise or is it hands-off after the initial provisioning?
Or say a new version of PHP is released. Does Forge go install it on all your servers automatically?
Not automatically, but there are buttons to click to do it
I use PHPloy to deploy the changes. Although it is manual, the good thing is it only deploys changes based on files changed in commit files in Git, so I don't need to deploy the whole app or remember which files are changed and should be deployed.
So if the deployed version in your server is on commit 1 while your local is on commit 3, it will only deploy changes in commit 2 and 3.
What's good about this is, if it's really really necessary, you can basically log in to your production server and change stuff quickly (for example to fix a very simple but very bad typo or some critical bugs) rather than having to go through the whole "make changes, git add, git commit, merge to master branch, then phploy" process.
I once tried both the manually git push from local then git pull from live (or setup an automated git hooks), but when I tried to do a production change above, it ends up making the repo in the production server having a staged git changes, making the future git pulls fail because there is an ongoing change not yet committed. I could manually git add then push in production then pull the changes to my local, but it ends up being a hassle.
Haven't really explored the envoyer (deploy to a release folder, then symlink the live version to that release folder) thing, because it seems to require quite a major change (since it requires storage and upload folders to be tweaked to survive changes between releases) and if the changes to be deployed is only a fix on typo in one file, it seems a bit overkill to deploy a whole release containing the whole app? I get that the advantages is we can roll back to previous releases quickly, but I find it easier to fix the breaking bugs quickly then deploying the necessary updates in the near future.
Of course this method works because I work in a quite a small team (< 5 developers), I'm sure it doesn't scale in bigger teams with more complicated deployment processes.
One killer option for me on the shared Hosting, I just learned that Laravel's/Filament database notifications doesn't work on Shared Hosting, only on VPS. To just test the functionnaloity, you need to queue:listen command in the terminal and stay there. So it's a killer function that shared hosting doesn't have.
Why there's no tutorial on how to deploy laravel in vps and no tutorial on how to deploy laravel webscoket
Thank you, but I've got a question. Why no any info about compiling js&css with nodejs for frontend? How do you handle it on server? Is it possible to run compiling process on forge?
It's a separate topic, wasn't discussed in this survey, deserves a separate video/survey probably, some day.
Thanks for this video. I use Google App Engine (serverless) Standard with Google Cloud SQL for laravel. It is very simple to setup, scale and deploy. I am surprised this is not used as often.
Laravel is a failure considering this survey. Shared hosting? No git? That s a disaster. Laravel is not for cheap projects. Don't use it, better use something else...
22dollars per month vs 35dollars per year, that's why people generally use shared hosting for small projects. also heroku is not bad
Laravel forge too expensive for me $12+$5 = $17 (RM71.03/month)
Clearly one of the best explanations on the topic. I think that, specially for juniors it is a headache when you start deploying your project, as there are many ways to do so. I'm personally moving from Shared Hosting to DigitalOcean, to avoid headaches from setting a laravel project on a Shared Hosting
my company uses ftp but doesn't use git , how can implement git into their ftp server
Namecheap gives me a 1 click update from git which I loveeee
I might even write a script to do automatic pulls from the main branch
My day: *sigh*, then run...
I guess all the survey has a "bias": all answers stems from the background everyone has.
Nonetheless, the video is very informative.
Even if I have a Mac OSX system available, for instance, I prefer to develop Laravel Apps on a Debian machine configured with specs that are very similar, if not identical, to the intended production server (VPS and/or Dedicated Server) with a "git" workflow.
Debian has a very stable LTS branch (the best, I should say, and this is because many Linux distros are derived from Debian). That guarantees no hassle while developing/deploying and during the maintenance phase. Sometimes by writing simple scripts you can recreate a similar workflow to Forge or other excellent services around.
Of course, that means you need to have intermediate skills to manage a server that is not the case for many developers.
I like having perfect control of the production server...especially nowadays where you can find cheap and scalable VPS.
Excellent Info, Keep the good work
What about a complete video tutorial from scratch and step by step using Forge and Digital Ocean??? It will be great...
Guess what... Search is powerful! :) ruclips.net/video/dzD7HI5lI1M/видео.html
Great video Povilas, i use cleavr.io, it is a bit more expensive than forge, but it has more tools and flexibility.
Git bare repos for deployment with git hooks for shared hosting
Thanks you very much Sir... I used to use ssh on shared hosting.
I recommend OVH, you can get a VPS at $4 with pretty good specs
Very bad costumer service
the whole yesterday i was thinking and searching how to deeply laravel
thanks man 😍
Hi i am from Iran, we can not use aws or digital ocean
Thanks for this interesting video. I use Laravel Vapor and was surprised it didn't come up more. I hate server administration stuff and find Git a little difficult, and I like the auto-scaling, so this was a great option for me. I will have to see how the costs are in the long run, though, and whether it's the best option for all my sites.
Same my company also works directly on live server LOL
it was my comment
Finally, someone agrees with me on Laravel Forge's Automatic Deployment is rather risky for a production server. Personally, I've never used it. Always have my Forge open in a browser tab. Doesn't take me 5 seconds to push deploy. I'd just rather not have some code I merged but haven't tested, go up to the live server.
Create two branches one for production and another one for staging. From your computer you push to staging and after confirming that everything is ok you merge to production and your live server will update without any risk ;)
heroku or digital ocean
PPT was well formatted n thanks to explain us 💯💯💯
Great content! Very useful insight. Thanks for sharing this. :)
i use forge, it worth every cent
I would like to ask, why anybody didnt mentioned azure? Is azure bad cloud for website development?
2 or 3 people mentioned Azure, not enough to make it to the stats. I guess it's not a "standard" environment for Laravel and needs extra configuration to make it work.
HI I am still learning QAP and I am having a problem deploying Laravel vue project to shared hosting. Can someone help me with it?
Hi, I don't recommend shared hosting for any Laravel project, especially with Vue. My recommendations: laraveldaily.com/what-server-is-needed-to-deploy-laravel-projects/
I have been using Ploi for last few months and very happy with it
What's that please
@@igbokwelaurence5882 Its paid service that manages your server. It works great for setting up Laravel apps. You can choose from multiple vps providers including linode or digital ocean.
Really useful research, thank you
sir, do you have recommendation for export data to pdf format with customable template?
No package would have customizable templates for your specific needs, you need to build it yourself
it is really interesting topic. with laravel deployment you always need vps to use laravel features like queues (redis) which you cannot get on most of shared hosts. there pros and cons for both hosts. with vps i faced 1 issue how to setup emails send and receive this was the reason i moved to shared host where email server is already setup you are receiving and sending emails with ease. i am using shared host with ssh and gitlab to deploy my laravel projects but there were some issues like no composer installed, older version of PHP cli (5.4) which will not allow you install composer and latest versions of laravel. fond solution to install composer on shared host. with help of .bashrc and .bash_profile able to update php cli version and composer command available to run composer and install latest version of laravel. But you cannot install redis or other os packages on shared host. still looking for a solution for VPS with email server up and running to receive emails.
Have a look at Mailgun
@@mikevwoods for sending emails mailgun is fine. But for inbound emails you need to pay 35$ per month which still expensive compare to shared host.
@@popetgirl you're right, way too expensive compared to shared hosting for inbound , but ideal if you are only doing low volume outbound.
For deployments I recommend to check out buddy.works , its so easy to use and very customizable. Its free up to 5 projects and 120 executions/month.
I use DigitalOcean, deployer.php, Jenkins and GitHub.
I have git and Plesk on my VPS. There is sometimes pain in the butt, since Plesk only supports single SSH key for Git repository and I have to create a new one and add it to ssh agent every time I use git pull. But, yeah - git and ssh is the case
I would recommend AWS lightsail which essentially EC2 infrastructure for smaller projects.
I use AWS Lambda to deploy my Laravel Applications.
You are great
Nice research
Can someone tell me why there is no azure ?
Because it's not popular/convenient for Laravel projects.
Most of the clients have their own shared hosting, in which we deploy THEIR web applications.
I sometimes use CI/CD with git for deployment on shared hosting, then I use ssh to create symbolic link and also to migrate, I also do add migration routes to the super admin group.
thank you
Tip for the next survey.
Use more checkboxes, radio buttons and select boxes, and less textareas. It will definitely help with summarising and visualising the data.
As it mentioned Laravel Forge with Digital Ocean is $22/month. Shared hosting can be 10 times cheaper and easier to operate for beginners - this makes sense for small projects.
how about serverless like aws lambda?
I guess my audience doesn't go serverless, no one mentioned it in the survey
Hi there, good free alternative for forge is ploi.io. IMO better for deploying laravel projects.
Free you say?
@@chuksadirije3353 One server, one site is free
If you need a GUI I recommend plesk stack on AWS lightsail.
Hi Sir, could you kindly tell me what digital ocean service that you use for your projects? Thank you :D
run ...
I am surprised ooh!!! No Heroku?
3 people mentioned Heroku, not enough to include into the chart
If you deploy laravel skip ovh hosting, its don t work.
presonally I stopped using shared hostings as VPS is just easier to maintain than wandering around some web panel
does anyone have a tutorial on deploying laravel to digital ocean and set mysql database? I keep getting time out and now i'm out of idea
Good insides
I use Jenkins + digital ocean. Sometimes I also work on live server 😅
Hey very nice to see. On note here: I am working in market research (yes, powered by laravel :)) and I would recommend, for any upcoming surveys, to use options instead of open answers. Not only is it easier for you to gather the answers, but it will also result in a much higher participation rate. Just my 2 cents and thank you for your work. My team learned a lot from your channel!
Been using Ploi and am happy with what they have to offer.
Shared hosting + git ?? That's interesting, though I understand it can be unsafe and I can't imagine managing Laravel migrations.. might be a pain at the end. Im surprised no one mentioned Heroku. It's free, you can use a domain name (have to register a credit or debit card) pricing starts at 5 which is very similar to those mentioned in the video, I do not own a paid account but often times I've been tempted to pay for one, the deployment is easy as pie too once you have everything configured. Nice video!
3 people mentioned Heroku, so it didn't come up on the list.
Its much simpler than you think. I also use the git function on my cPanel to deploy projects and there is a button that pulls your changes from git. cPanel connects to github for example through ssh by generating an ssh key which you add to your git repo so a secure connection is established. There is also a Terminal in cPanel that I use to run composer and artisan commands if I don't want to use an ssh client. Then finally the CRON manager for task scheduling.
what is the best plan in Heroku i should choose for laravel projects ?
@@felixmensahafedzo70 any toturial to how to use heroku with laravel ?
@@MrError-ml3lz I have the free plan. I think if you're anything like me, a novice Laravel developer and want to start deploying you should consider that service, it's easier than shared hosting + it is free. However as @mensah felix replied, shared hosting might have it's advantages, I just haven't deployed any websites with shared hosting + git.
Hetzner, Github Actions
I use Bluehost for all of my projects. I only pay 15$ per month and I get pre configured server with ssh, git. and with one account I can host ‘unlimited’ projects with ‘unlimited’ storage & email. I have 2 accounts with about 6 projects each and everything is working fine. No problem, no slowing down and deploying using git. Mind you tho, all my projects have relatively low traffic
What plan you are using ? Shared, VPS or dedicated ? Im looking for an afforadable hosting, to deploy a laravel project on a budget
Hello, Im currently using Laravel Forge to deploy my applications on AWS, however i cannot find where the databases are stored. I have looked under RDS and the other server options, however i cannot find it. Do you happen to know where the databases are stored when you deploy to AWS through forge? Thanks
Have you tried swapping the region? Sometimes u are on west and it was created on east .
Thanks very much for this video, very useful :). I have a question, I am currently working on a quite big project using laravel with jetstream+inertia and I was thinking of deploying maybe with digital ocean or Google cloud service , laravel forge is the best way to do it? Could you orient me into what I should look into to study please
Thank you
You don't know until you TRY. No one can tell you what is the best for YOUR scenario. But I do advise Forge + Digital Ocean as the *easiest* entry level.
Very useful content. Thanks for your work!
If you use forge, can you have more than one laravel app per forge-managed server? Or is it one server per laravel app? Because if you can have multiple, let's say 2-3, low traffic sites per server, the cost is not very high i think.
Yes you can have multiple projects per server
I use heroku now. It's the best free option and offers CI/CD pipeline imo. Zero cost for compute as well as storage
Exactly, easy to use.
We primarily use Jenkins to pull, build, test via docker etc then SCP artifacts to destination (mainly for removing link to git on application servers), rebuild and symlink live. A nice way of ensuring we never mutate or destroy old deployments. There was a great tutorial done during a past laracon on using Jenkins with laravel for anyone wanting to learn more
Give a link to the laracon pls
Shared hosting actually shocked me also. I have run a quick app before on a reseller package but sometimes server resources are just not great on them.
I now use Ionos VPS as they offer great deals and half price for 6 months most of the time.
You can use Azure DevOps to deploy on a shared server using git hooks.
I used to do it 2 years back for low-paying clients.
I'm using GCP
What software do you use to record your screen?
Camtasia Studio on Mac
Looking at the first slide, if you haven't already you should add a digital ocean affiliate link to your RUclips videos
I don't do affiliate promotions on this channel, I prefer to earn from my products, meanwhile reporting *unbiased* information from the market :)
@@LaravelDaily completely understand that! Thanks for the great content
I was using WebFaction for almost a decade but when it shut down (was bought by GoDaddy) I migrated all of my sites to OpalStack. Yes, I've choose shared hosting option, but as WbFaction did have, I comes with SSH, Git, and almost all of the stuff I need for smaller projects. So far I am very satisfied and I can recommend it to everyone who needs a decent shared hosting plan.
Can you explain how is the process to deploy a project in OpalStack ? Im new with Laravel and never did a deployment :S
@@insurg3nt3 It is simple. You need a git (I use BitBucket because it was free when I started and I am a bit lazy to transfer everything to another service). Then it is just a matter of enabling git in your project, commit and push changes to BitBucket. Then I SSH to OpalStack, into my project and simply git pull everything from BitBucket. This last step was one which I am hoping Povilas will go a bit deeper in one of his next videos. OpalStack has a good tutorial on how to start Laravel app on their shared hosting.
@@VladimirMarkovic Thank you man :)
Thanks!
Your videos are so clean and detailed thanks again, can you do a video on how to do docker on laravel and sail package?
It's not popular enough to make it worth shooting the video.
@@LaravelDaily yeah sail is not popular but docker is very popular also very important when it comes to deployment like load balance and more and also for team based project, maybe can you ask people's if it is worth making video like make a vote on Twitter if you get many votes maybe then do a video 🙄
In small projects it's better to use Codeigniter or other framework who doesn't rely on terminal, but thinking again ssh/terminal access is needed when need implement extra features.
Sir: I follow your all videos .
but if you find a time plz make social network series I search in youtube but not find a good series but ur way of teaching I understand ur teaching technique.
in social network all problem will cover that everyone have ...
Sorry, for now I'm not planning such series. For a *proper* social network, it would be a full course with huge length, like 5+ hours. I don't have that much time available, sorry, focused on other topics now.
I ssh into server, git pull, then create a copy of the git folder, run composer install and other stuff, then change symlink. If using php-fpm at this point you need to restart php-fpm. After confirming it worked i delete old folder the symlink used to point to
Google cloud?