Roadhouse question

Tue, 11 Jan 2022 15:02:49 +0100

tombeau

tombeau@ein-hub-von-vielen.de

@Zap Do I have to do something on Roadhouse like a "composer update" you mentioned. Why? Both of my Roadhouse instance stopped to work.

Roadhouse

show all 8 comments

Tue, 11 Jan 2022 15:06:31 +0100

tombeau

tombeau@ein-hub-von-vielen.de

dev branch, automatic util/udall daily at 05:30 (Berlin/Amsterdam)

Tue, 11 Jan 2022 19:19:58 +0100

tombeau

tombeau@ein-hub-von-vielen.de

@Zap The "composer" seems to be missing.

I followed #^https://getcomposer.org/doc/00-intro.md

util/udall runs again

Now I have two other issues

1. I did not find a way to get rid of the required user input "yes" (compser is asking every time "Continue as root/super user [yes]?") if I run /var/www/zotcron.sh. This needs more investigation from my side. I am thankfull of any ideas. Yes, I am aware of #^https://getcomposer.org/doc/03-cli.md#composer-allow-superuser
2. Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0". is shown if I open one of my instances for example #^https://misty.digitalesparadies.de/

I guess it is time to upgrade Debian and PHP.

Tue, 11 Jan 2022 20:19:34 +0100

tombeau

tombeau@ein-hub-von-vielen.de

Debian is now updated from 10 to 11 and PHP is updated to 7.4.x

Result: Roadhouse works again

Tue, 11 Jan 2022 21:06:20 +0100

tombeau

tombeau@ein-hub-von-vielen.de

export COMPOSER_ALLOW_SUPERUSER=1

Seems to eleminate the required user input (for composer) when running /var/www/zotcron.sh as root.

Tue, 11 Jan 2022 21:10:57 +0100

Zap

zap@z.macgirvin.com

Added COMPOSER_ALLOW_SUPERUSER to the script (when appropriate) so it doesn't go interactive.

Tue, 11 Jan 2022 21:18:21 +0100

tombeau

tombeau@ein-hub-von-vielen.de

> Added COMPOSER_ALLOW_SUPERUSER to the script (when appropriate) so it doesn't go interactive.

Good idea thanks!

Tue, 11 Jan 2022 21:40:49 +0100

tombeau

tombeau@ein-hub-von-vielen.de

> Added COMPOSER_ALLOW_SUPERUSER to the script (when appropriate) so it doesn't go interactive.

I just tested this during the upgrade to Debian 11 (Raspi) of my second instance. Yes, it works.

Both servers are upgraded and running again.

Tue, 11 Jan 2022 22:02:23 +0100

tombeau

tombeau@ein-hub-von-vielen.de

@Papa Dragon

Somebody should add "composer" to the .homeinstall.

If no one is faster I can add this and test in a virtual maschine. (I am on holiday at the moment. So it won't happen in the next days.)

Does anybody know if there will be a difference (for ZAP, Roadhouse, Streams,...) if composer is intalled using apt-get

apt-get install composer

see #^https://packages.debian.org/bullseye/composer

This would be my preferred way instead of using...

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === '906a84df04cea2aa72f40b5f787e49f22d4c2f19492ac310e8cba5b96ac8b64115ac402c8cd292b8a03482574915d1a8') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"
mv composer.phar /usr/local/bin/composer

@Zap Any idea?

I guess the line

php -r "if (hash_file('sha384', 'composer-setup.php') === '906a84df04cea2aa72f40b5f787e49f22d4c2f19492ac310e8cba5b96ac8b64115ac402c8cd292b8a03482574915d1a8') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"

will change over time and one should not include this check into the .homeinstall.