quickstart-basic VS starter-workflows

For this blog post, we will containerize the sample Laravel task-list application provided on GitHub. This project was written against a reasonably old version of Laravel and has since been archived. However, working with this codebase requires that we address a number of requirements commonly found in production and legacy code bases, such as using specific versions of PHP, database migrations, port mappings, and running integration tests.

Now that we have the basics in place, let's take things up a notch by introducing GitHub Actions. GitHub Actions allows us to automate various tasks like running tests, building, and deploying our application directly from our repository. In this blog, we’ll specifically focus on the CI (Continuous Integration) part to automate API testing for our Express app.

StyleSpark is a productivity tool designed to help developers gain insights into their coding styles by analyzing their code snippets and matching them to the styles of iconic programmers. Specifically, it is a new GitHub Action that programmers can include in their workflows to inspire personal growth and improvement in coding practices by providing users with a fun and educational way to explore different programming styles. It leverages Llama 3 to analyze snippets from your GitHub repos to identify how your style compares to computing's heroes! When it's done, it will update your README with a snazzy badge powered by Shields.io, like this one:

Jenkins and GitHub Actions are go-to tools for automating tasks like testing and deployment. These pipelines ensure that the latest version of your software gets built, tested, and delivered efficiently.

Using tools like GitHub Actions or CircleCI.

Más ejemplos de pipelines CI/CD

This guide will walk you through a comprehensive and straightforward approach to configuring GitHub Actions for Vue and Vite applications and using GitHub Pages for deployment, providing you with a clear and practical roadmap to implement CI/CD pipelines from scratch.

We use GitHub Actions to set up our CI/CD. The infra team (they renamed themselves to 'DevOps' a few years ago 🤔) set up a pool of runners for us and shared the IaC (Infrastructure as Code) repository for provisioning them.

There are a lot of tools that could help with making CI/CD pipelines, but for this project, I decided to go with Github Action, this was because I was already familiar with it and it would be a perfect fit for my project

GitHub Actions is a cloud-based CI/CD solution built into GitHub’s ecosystem that enables developers to automate workflows directly within their repositories. It supports workflows triggered by events known as actions such as code pushes, pull requests, and issue events, making it a great solution for teams already using GitHub for version control.

Pro Tip: Use docker-compose to manage multiple containers locally, and integrate Docker with CI tools like Jenkins, GitHub Actions, or GitLab CI for seamless automation.