search

rewardenv / reward

Reward is a Swiss Army knife CLI utility for orchestrating Docker based development environments.
https://rewardenv.readthedocs.io
MIT License
89 stars 13 forks source link

Composer 1 being used instead of Composer 2 #33

Closed ghost closed 1 year ago

ghost commented 1 year ago

Steps

  1. Clone Magento project
  2. Modify .env (optional)
  3. Import db
  4. Run reward bootstrap

This was working fine with Composer 2 until I updated rewardenv, now whenever I start a project it appears that it uses Composer 1 to install the dependencies when Composer 2 is recommended.

Also, I've tried using sudo alternatives --config composer to select the version Composer, but when I run the bootstrap command, it uses Composer 1 again

Screenshots

Untitled

janosmiko commented 1 year ago

Hi @leoner-omnipro !

Could you provide your .env file, and your reward version please?

In an older version of Reward it enforced the Composer version based on the Magento version (enforce to use composer2 for magento 2.4.2+ or something similar) but I removed that as someone requested to remove it.

Now you can enforce the composer version using the COMPOSER_VERSION=1/2 variable in the .env file.

ghost commented 1 year ago

Hi @leoner-omnipro !

Could you provide your .env file, and your reward version please?

In an older version of Reward it enforced the Composer version based on the Magento version (enforce to use composer2 for magento 2.4.2+ or something similar) but I removed that as someone requested to remove it.

Now you can enforce the composer version using the COMPOSER_VERSION=1/2 variable in the .env file.

Sure, here the reward version image

and the .env file

REWARD_ENV_NAME=testing-magento
REWARD_ENV_TYPE=magento2
REWARD_WEB_ROOT=/

TRAEFIK_DOMAIN=testing-magento.test
TRAEFIK_SUBDOMAIN=
TRAEFIK_EXTRA_HOSTS=

REWARD_DB=1
REWARD_ELASTICSEARCH=0
REWARD_OPENSEARCH=1
REWARD_OPENSEARCH_DASHBOARDS=0
REWARD_VARNISH=1
REWARD_RABBITMQ=1
REWARD_REDIS=1
REWARD_MERCURE=0

ELASTICSEARCH_VERSION=7.16
OPENSEARCH_VERSION=1.2
MARIADB_VERSION=10.4
NODE_VERSION=16
PHP_VERSION=7.4
RABBITMQ_VERSION=3.8
REDIS_VERSION=6.0
VARNISH_VERSION=6.5
COMPOSER_VERSION=2

REWARD_SYNC_IGNORE=

REWARD_ALLURE=0
REWARD_SELENIUM=0
REWARD_SELENIUM_DEBUG=0
REWARD_BLACKFIRE=0
REWARD_SPLIT_SALES=0
REWARD_SPLIT_CHECKOUT=0
REWARD_TEST_DB=0
REWARD_MAGEPACK=0

BLACKFIRE_CLIENT_ID=
BLACKFIRE_CLIENT_TOKEN=
BLACKFIRE_SERVER_ID=
BLACKFIRE_SERVER_TOKEN=

XDEBUG_VERSION=
janosmiko commented 1 year ago

I think I found the issue. I will publish the fix tomorrow. Stay tuned 👌

janosmiko commented 1 year ago

It should be fixed now. @leoner-omnipro please let me know if the issue still occurs with v0.3.25-beta

ghost commented 1 year ago

It should be fixed now. @leoner-omnipro please let me know if the issue still occurs with v0.3.25-beta

Working again! Only this warning appears, but I don't think it's anything to worry about.

image