Can't use module on SC platform

[brynwhyman]

Background

It looks like the same issue was previously resolved for the CWP platform, and while there are notes explaining the fixes were tested on SC, we've had reports of issues

Related issues:

• Can't use module on CWP platform #113
• Errors occur trying to write composer caches #121
• FIX Don't blindly assume that HOME is writable silverstripe-composer-update-checker#43

Further information

We've had an internal report of this here: https://silverstripeltd.slack.com/archives/CLXKD9X51/p1583114132100800

[brynwhyman]

Excuse the very much internal reference in an open source issue - but given that this is likely installed on a number of projects in on the Silverstripe Cloud platform, I'm hoping we can use it to elicit some feedback from others.

[brynwhyman]

I count this module being used on 24 production environments on our own SC platform.

[rafaeldsousa]

I believe what I'm experiencing is related, just started happening for one of my SC sites.
Error: E_WARNING: chdir(): Permission denied (errno 13)

SS had a look and could trace it down to this module, but couldn't tell me why the permission error was happening.

From SS
Odd, this is part of the UpdatePackageInfoTask in the silverstripe-maintenance module and its coming up during the queued job run but the task is not being run.

https://github.com/bringyourownideas/silverstripe-composer-update-checker/blob/master/src/Extensions/ComposerLoaderExtension.php#L111-L127

silverstripe-maintenance/src/Util/ComposerLoader.php

Line 65 in d1435bb

$this->extend('onAfterBuild');

[brynwhyman]

Hey @rafaeldsousa, what version of this module (bringyourownideas/silverstripe-maintenance)
and bringyourownideas/silverstripe-composer-update-checker are you running?

[rafaeldsousa]

Hi @brynwhyman
bringyourownideas/silverstripe-maintenance - 2.3.1

bringyourownideas/silverstripe-composer-update-checker - 2.0.3

[andrewandante]

Just to add - I've just seen this behaviour. It breaks all dev/tasks for me, because composer isn't installed on the SCP servers. This means that neither HOME or COMPOSER_HOME are defined, and it throws a server error:

error-log.ERROR: Uncaught Exception RuntimeException: "The HOME or COMPOSER_HOME environment variable must be
set for composer to run correctly" at /var/www/mysite/releases/63e07fc364b9f90ab583e83a6f04bb72a26faf20/vendor
/composer/composer/src/Composer/Factory.php line 652 {"exception":"[object] (RuntimeException(code: 0): The HOME 
or COMPOSER_HOME environment variable must be set for composer to run correctly at /var/www/mysite/releases
/63e07fc364b9f90ab583e83a6f04bb72a26faf20/vendor/composer/composer/src/Composer/Factory.php:652)"}

[brynwhyman]

@michalkleiner shared a theory in a duplicate issue, thinking the usage of the syntax in the prior fix might be off.

See: silverstripe/cwp-recipe-basic#4 (comment)

[GuySartorelli]

I believe this should be closed - seems to be working fine now.

[michalkleiner]

@GuySartorelli doesn't work for us on CWP nor on AWS with private repos due to some permission issues. If this module is an umbrella module for the security checker and update checker, then the issues still exist.