I would like to know how do developers works after the project was pushed to production. Is somehow Github project is connected to hosting and whenever there is a new version on master branch it will be reflected on the hosting automatically?
Which hosting is more suitable for Laravel/Lumen rather than Forge (It is too expensive for me)?
Thanks in advance! Laracasts community is the best!
@abdulaziz I set up a remote repository on the production server where I can push up changes. I then have an on-receive hook which runs a script that applies the code changes and executes any tasks (artisan command to recache configs, npm, gulp, whatever)
So, in other words, I type 1 command and the magic happens.
For example, to push all changes on the master branch to the production repository: git push master production
This tutorial helped me learn the basics to set it up:
As for hosting, I can't provide much insight. Fortunately, I deal with large companies that handle their own hosting servers. I see that DigitalOcean is quite popular for Laravel applications.
I deploy my changes with GitFTP-Deploy. You can basically commit your changes to production that way. Works good. One thing I still have to figure out, is how to go about running migrations and composer (vendor) updates. Ideally, when deploying php artisan migratie and composer update (not sure if that one is correct) are run.
