- Home
- » Tags
- » deployment
deployment
-
https://github.com/magenx/Magento-2-server-installation
One-command installer that provisions a hardened LEMP web stack with Nginx, MariaDB, PHP-FPM, Varnish, Redis, OpenSearch, RabbitMQ, and Let’s Encrypt on Debian/Ubuntu. Also outlines SSL setup and a zero-downtime deployment pattern (current/releases/shared) with GitHub Actions.
88211 -
https://github.com/elgentos/magento2-static-deploy
A high-performance static content deployment tool written in Go that significantly accelerates Magento 2 static asset deployment by leveraging true parallelization and efficient file I/O.
1183 -
https://www.sdj.pw/posts/magento2-patching/
Deploying patches is simple for in-house development teams or smaller Agencies maintaining only a few stores. Manually applying patches per project is simple, but doesn’t scale well. Both from time cost and security exposure perspectives.
-
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://dor.ky/posts/2024/10/hyva-not-generating-hyva-themes-json-magento-2-4-7/
At work this week I was updating the deployment scripts for one of our projects
when I realised that Hyva wasn’t generating the app/etc/hyva-themes.json
file on deployment which then caused the pipeline to fail. -
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?