From e7542293d6db519cce10f5d55c079a4f21482c2b Mon Sep 17 00:00:00 2001 From: Jocelyn Jaubert Date: Mon, 15 Nov 2021 22:51:38 +0100 Subject: Launch yarn before linking to new peertube version If yarn fails because we don't have the correct nodejs version, we want to know earlier, so that we can upgrade nodejs without having a non-working half-installed peertube instance. --- scripts/upgrade.sh | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'scripts') diff --git a/scripts/upgrade.sh b/scripts/upgrade.sh index 59dc5ab26..9c17aecb8 100755 --- a/scripts/upgrade.sh +++ b/scripts/upgrade.sh @@ -68,11 +68,13 @@ cd $PEERTUBE_PATH/versions unzip -o "peertube-${VERSION}.zip" rm -f "peertube-${VERSION}.zip" -# Upgrade Scripts +# Launch yarn to check if we have all required dependencies +cd "$PEERTUBE_PATH/versions/peertube-${VERSION}" +NOCLIENT=1 yarn install --production --pure-lockfile + +# Switch to latest code version rm -rf $PEERTUBE_PATH/peertube-latest ln -s "$PEERTUBE_PATH/versions/peertube-${VERSION}" $PEERTUBE_PATH/peertube-latest -cd $PEERTUBE_PATH/peertube-latest -NOCLIENT=1 yarn install --production --pure-lockfile cp $PEERTUBE_PATH/peertube-latest/config/default.yaml $PEERTUBE_PATH/config/default.yaml echo "Differences in configuration files..." -- cgit v1.2.3