2020-05-08
3346
#laravel
Michael Okoh
18258
May 8, 2020 â‹… 11 min read

How to create a CI/CD for a Laravel application using GitHub Actions

Michael Okoh I code, that's all.

Recent posts:

Hand holding purple sticky notes for CSS sticky positioning guide.

Troubleshooting CSS sticky positioning

Fix sticky positioning issues in CSS, from missing offsets to overflow conflicts in flex, grid, and container height constraints.

Ibadehin Mojeed
Nov 13, 2024 â‹… 5 min read
Task Scheduling and cron Jobs in Node Using node-cron

Scheduling tasks in Node.js using node-cron

From basic syntax and advanced techniques to practical applications and error handling, here’s how to use node-cron.

Godwin Ekuma
Nov 12, 2024 â‹… 7 min read
Working With The Angular Tree: Flat Vs Nested Trees And More

Working with the Angular tree

The Angular tree view can be hard to get right, but once you understand it, it can be quite a powerful visual representation.

Lewis Cianci
Nov 12, 2024 â‹… 21 min read

Why you should use SWC (and not Babel)

In this post, we’ll compare Babel and SWC based on setup, execution, and speed.

Kasra Khosravi
Nov 12, 2024 â‹… 9 min read
View all posts

9 Replies to "How to create a CI/CD for a Laravel application using GitHub Actions"

  1. Wow this is a very great article thank you very much and is very long you should consider splitting it into parts and also the ssh key and ip address is exposed in this article; you should consider hiding it. But overall this is a very helpful article. I am grateful for taking your time to write it.

  2. Awesome article, you might want to add these if your workflow fails at the deploy stage

    `set(‘composer_options’, ‘install –verbose –prefer-dist –no-progress –no-interaction –optimize-autoloader’);`
    `set(‘writable_mode’, ‘chown’);`

  3. Hey! Thank you for this great article!
    I have a question: why do you run “composer install” inside the git action and not on the server when deploying it? I feel like this would save some time, since most of the dependencies are already on the server…?

  4. In the deploy.php file, the require statements is looking for laravel.php and rsync.php in a recipe folder at the project root level. The article doesn’t mention anything about creating the recipe folder and copying those files from vendor\deployer\recipe.

    Also, when installing deployer and deployer recipes, I got a yellow notice saying that deployer recipes and deployer phar– projects have been abandoned. Has anyone take over these packages or found alternatives?

  5. Can anyone please help to run artisan command on deployment. How can I execute php artisan migrate and other commands.

Leave a Reply