ci-cd
-
https://github.com/comwrap/com-acc-api-mesh-ci-cd
This repository is a lightweight starting point for teams that want a repeatable GitHub Actions pipeline for provisioning and updating Adobe API Mesh configurations. Fork it, drop in your mesh definition files, wire up the required Adobe Developer Console credentials, and you will have a push-button deployment path for staging and production meshes.
-
https://www.linkedin.com/pulse/magento-2-deployment-using-deployer-gitlab-pipelines-andrei-litvin-yjgff/?trackingId=P37sYlyOSf2dlSWtNn%2B90A%3D%3D
This post explains how to set up a deployment workflow for a project using Deployer and GitLab Pipelines, including steps to build a new release, package it, and deploy it to a server via SSH. The article outlines creating a custom Docker image, configuring SSH access, and defining a .gitlab-ci.yml file to automate the deployment process. It serves as a guide for developers looking to implement similar workflows.
-
https://github.com/magenx/Magento-2-deployment-pipeline
This repository provides a template for setting up a SOC 2 compliant process using release-please-action on GitHub Actions. The workflow automates version control, changelog generation, pre-release => release creation, deployment and PR comments.
618 -
https://github.com/lbajsarowicz/magento2-config-validator
The module answers one of the most common mistakes made when maintaining Magento 2 projects.
Outdated config.php file in the repository leads to serious issues with environment consistency after the deployment.
When your Deployment Configuration is not in line with the codebase, exit code is 1 (ERROR)
-
https://www.michiel-gerritsen.com/make-magento-update-automatically/
Automatic Magento Updates. It is the ultimate utopia. Or is it? Is it really possible? How do you manage that? And what if an update contains bugs?