The problem that leads to the issue described below is that the app queue does not realize that Magento has been installed because it does not have access to the .config/* files created by the deploy script. The solution is to move non-log mounts to a shared network storage.

Preconditions (*)

Use an unmodified Magento Marketplace Template

Steps to reproduce (*)

1. Create project
2. The app worker will not recognize that Magento has been installed. Wait a few minutes, the app queue log will start populate with warnings about the queue command
3. Wait 24 hours or so, the disk space will fill completely.

Expected result (*)

1. The app worker has all commands available to it because it recognizes that Magento has been installed.

Actual result (*)

1. See steps to reproduce and description.

Redeploying environment master
Closing services app, app--queue, and router
Opening applications app, app--queue and their relationships
Executing deploy hook for application app
Starting Magento installation:
W:
File permissions check...
W: In Installer.php line 909:
W:
W: Missing write permissions to the following paths:
W: /app/app/etc
W:

Summary (*)

The Multi Source Inventory module is not present. MSI was added in 2.3, wondering has it been deliberately left out or removed?

Examples (*)

Proposed solution

Move to the latest upstream version 2.4 and add Elastic Search to this repo

Hi,

When I use the default cron spec in the template it won't push up due to the following error message.

"The minimum interval between cron runs is 5 minutes, even if specified as less."

I guess because the cron spec in the platform.app.yml is

crons:
    magento:
        spec: "* * * * *"
        cmd: "php bin/magento cron:run"

Should it not be?

crons:
    magento:
        spec: "*/5 * * * *"
        cmd: "php bin/magento cron:run"

Cheers Dan

Title says it all -- just tested a few times the default Magento template and noticed that several things are outdated.
Updating everything manually doesn't seem to be straightforward.

Also, latest 2.4.x Magento now requires Elastic Search instead of the database powered search, so adding that service by default would be great as well.

Thanks!

Describe the bug

last update workflow functionality has been moved into a reusable workflow. However, we still have the original version of it in a last-update.yaml workflow file.

Include some logs

https://github.com/platformsh-templates/magento2ce/actions/runs/5731621504/job/15532917629
fails because the copy of the workflow already ran

Reproducing

Accept a PR, watch the last updated workflow run 2X

Expected behavior

the last updated workflow should only run 1X

Your environment

n/a

Screenshots

No response

Additional context

No response

What in this template can be improved or added as a feature?

https://github.com/Elpikachu/magento2-ece

What exactly should be updated?

Above

How important is this feature to you?

Above

Additional context

No response

Describe the bug

The template currently assumes that the database has no password (as it doesn't on platform.sh).

But it does on DDEV.

The --password arg should be provided.

Include some logs

Build failed w/ command: php bin/magento setup:install --ansi --no-interaction --skip-db-validation --base-url=https://platform-magento2ce.ddev.site/ --db-host=db --db-name=db --db-user=db --backend-frontname=admin --language=en_US --currency=USD --timezone=Europe/Paris --use-rewrites=1 --session-save=redis --session-save-redis-host=redis --session-save-redis-port=6379 --session-save-redis-db=0 --cache-backend=redis --cache-backend-redis-server=redis --cache-backend-redis-port=6379 --cache-backend-redis-db=1 --page-cache=redis --page-cache-redis-server=redis --page-cache-redis-port=6379 --page-cache-redis-db=2 --admin-firstname=admin --admin-lastname=admin [email protected] --admin-user=admin --admin-password=admin123

(Note that it doesn't pass the db-password)

[Progress: 4 / 705]
Installing database schema:

In Abstract.php line 144:

  SQLSTATE[HY000] [1045] Access denied for user 'db'@'172.17.0.3' (using password: NO)

It's failing because it's not using a password.

Reproducing

ddev get https://github.com/ddev/ddev-platformsh/tarball/main

ddev start

Expected behavior

Start

Your environment

DDEV v1.22.1

Screenshots

No response

Additional context

No response