Thank you JohnLivingston for your help. I now have node version 16. I am making progress. Here is where some problems start showing up. Install Peertube with internet connection on: cd /var/www/peertube/peertube-latest && sudo -H -u peertube yarn install --production --pure-lockfile 1259 packages. 1608. many warnings but no errors.
bullseye@debian:/var/www/peertube/versions$ sudo -u peertube unzip -q PeerTube-release-4.2.0.zip
bullseye@debian:/var/www/peertube/versions$ sudo -u peertube ln -s /var/www/peertube/versions/PeerTube-release-4.2.0 /var/www/peertube/peertube-latest
bullseye@debian:/var/www/peertube/versions$ cd /var/www/peertube/peertube-latest && sudo -H -u peertube yarn install --production --pure-lockfile
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @aws-sdk/lib-storage@3.72.0" has unmet peer dependency "@aws-sdk/abort-controller@^3.0.0".
warning " > @typescript-eslint/eslint-plugin@5.19.0" has unmet peer dependency "@typescript-eslint/parser@^5.0.0".
warning " > eslint-config-standard-with-typescript@21.0.1" has incorrect peer dependency "@typescript-eslint/eslint-plugin@^4.0.1".
warning " > eslint-config-standard-with-typescript@21.0.1" has incorrect peer dependency "eslint@^7.12.1".
warning " > eslint-config-standard-with-typescript@21.0.1" has incorrect peer dependency "eslint-plugin-promise@^4.2.1 || ^5.0.0".
warning "eslint-config-standard-with-typescript > @typescript-eslint/parser@4.33.0" has incorrect peer dependency "eslint@^5.0.0 || ^6.0.0 || ^7.0.0".
warning "eslint-config-standard-with-typescript > eslint-config-standard@16.0.3" has incorrect peer dependency "eslint@^7.12.1".
warning "eslint-config-standard-with-typescript > eslint-config-standard@16.0.3" has incorrect peer dependency "eslint-plugin-promise@^4.2.1 || ^5.0.0".
warning "swagger-cli > @apidevtools/swagger-cli > @apidevtools/swagger-parser@10.0.3" has unmet peer dependency "openapi-types@>=7".
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
$ test -n "$NOCLIENT" || (cd client && yarn install --pure-lockfile)
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > bootstrap@4.6.1" has unmet peer dependency "jquery@1.9.1 - 3".
warning " > bootstrap@4.6.1" has unmet peer dependency "popper.js@^1.16.1".
warning " > primeng@13.3.0" has unmet peer dependency "primeicons@^5.0.0".
warning " > wdio-chromedriver-service@7.3.2" has unmet peer dependency "webdriverio@^7.0.0".
[4/4] Building fresh packages...
Done in 101.09s.
Done in 174.99s.
bullseye@debian:/var/www/peertube/peertube-latest$ I guess all these warnings are normal and can be ignored? And what are the 1259 packages? It seems they are automatically downloaded from somewhere. I would think that PeerTube-release-4.2.0.zip should contain these. Can they all be put into an archive file? Then 1608 installations? I like to download everything first, then turn off internet connection before running install. But I can change if needed.
I do not know what to change in the production example configuration: /var/www/peertube/config/production.yaml. So I do not change it.
The nginx configuration template /etc/nginx/sites-available/peertube says you need a certificate to run in production. This seems to be my current biggest problem. I am trying to setup peertube to run on off-line localhost. Of course I can invent my own domain name there. How to get a certificate? Are there other ways to run other than production?
I will be away for several weeks and will return in July 2022.