magento / magento/magento-cloud

Improving the installation process of the magento Cloud template

Open
#529 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
226
Forks
244
PR merge metrics
No merged PRs in 30d

Description

Hi,

The installation process of this cloud template has multiple pain points compared to community/enterprise edition.
As a consequence, it is quite complex to maintain a dev tool chain that automates the creation of a Magento project.

Here are the main issues:

1. This repository is not hosted on packagist:

- Initializing a Magento community/enterprise project: `composer create-project`.
- Initializing a Magento cloud project: `git clone -b 2.4.4 --depth 1 git@github.com:magento/magento-cloud.git `.

2. In composer.json, the `require-dev` section is missing. So in our boilerplate, we have to create a temporary Magento enterprise project (with `--no-install` option), get the dev packages list with `composer show -s` (involves using sed and grep to filter the output...), and add them to the Magento cloud project with `composer require`...

It's standard practice to include dev packages by default. On a production environment, you are supposed to run composer with the `--no-dev` option.

3. The `autoload-dev` section is not up to date. The following entry is missing:

```json
"autoload-dev": {
"psr-4": {
"Magento\\PhpStan\\": "dev/tests/static/framework/Magento/PhpStan/"
}
}
```

This missing entry cannot be added with the composer command-line, so the only way to add this missing entry is to edit the file manually.

edit: I would also suggest the following improvements:

- Removing the composer.lock file from this repository.
- Settting the min stability to "stable".

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting composer.json and composer.lock in the repository and compare the cloud template's installation flow with the community and enterprise flow described in the issue. Determine the intended handling for require-dev, autoload-dev, the lock file, and minimum stability. Done means the agreed installation improvements are represented in the repository and the resulting Composer workflow is validated.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.