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:

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
what's new in next js 15.4

Next.js 15.4 is here: What’s new and what to expect

Next.js 15.4 is here, and it’s more than just a typical update. This version marks a major milestone for the framework and its growing ecosystem.

Abiola Farounbi
Jul 29, 2025 â‹… 6 min read
React logo over a dark blue abstract background with glowing network nodes and connections

Build interactive React UIs for LLM outputs using llm-ui

If you’re building an LLM-powered application, llm-ui is a powerful tool to help you add structure, flexibility, and polish to your AI interfaces.

Emmanuel John
Jul 29, 2025 â‹… 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