[09:44:10]
<freetux> `/opt/node_n/n/versions/node/22.22.3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin`
[09:44:49]
<artlog> ls -la /opt/node_n/n/versions/node/22.22.3/bin
[09:45:00]
<freetux> ```
$ ls -la /opt/node_n/n/versions/node/22.22.3/bin
total 121908
drwxr-xr-x 2 root root 4096 May 13 14:50 .
drwxrwxrwx 6 root root 4096 May 25 13:43 ..
lrwxrwxrwx 1 root root 45 May 13 14:50 corepack -> ../lib/node_modules/corepack/dist/corepack.js
-rwxr-xr-x 1 root root 124819136 May 13 14:50 node
lrwxrwxrwx 1 root root 38 May 13 14:50 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxrwxrwx 1 root root 38 May 13 14:50 npx -> ../lib/node_modules/npm/bin/npx-cli.js
```
[09:45:10]
<artlog> ok pas de pnpm , au vu des install c'est un corepack enable trucmuche qui fait le taff pour pnpm
[09:45:17]
<artlog> ah le miens est un peu dans le choux car j'ai joué avec ...
[09:45:25]
<artlog> le problème est sous nos yeux : le pnpm n'est pas installé pour cette version de node...
[09:45:32]
<artlog> c'est un peu infernal tout ça
[09:45:41]
<freetux> C'est clair.
[09:46:03]
<artlog> le corepack enable pnpm doit installer ce qu'il faut mais il y des variables d'environnment à mettre et il faut l'exécuter en root globalement, c'est pourquoi je dois tester avant...
[09:46:31]
<artlog> le temps de resetter mon env de dev
[09:47:06]
<freetux> J’ai fait un petit récap sur github. ^^
[09:48:19]
<artlog> a partir de maintenant ça devrait allez mieux...
[09:48:34]
<artlog> cd /var/www/peertube
[09:49:13]
<freetux> J’imagine, et tous les autres que tu as il ne me les faut pas non plus ?
[09:49:51]
<artlog> NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production pnpm run plugin:install --npm-name peertube-plugin-auth-ldap
[09:51:39]
<freetux> npm
npx
yarn
yarnpkg
[09:51:51]
<artlog> peut etre npx, pour yarn il ne devrait plus etre utilise par peertube , pnpm le remplace
[09:52:28]
<freetux> Ça tourne ! 🥳
[09:53:18]
<artlog> npm et npx tu les avais éà
[09:53:51]
<freetux> Je vais relancer la mise à jour du coup dès que c’est terminé.
[09:54:08]
<artlog> oui c'est à tenter ...
[09:56:20]
<artlog> ça ne devrait pas être long...
[09:56:55]
<freetux> Oups 😄
```
"err": {
"err": {
"stack": "Error: Command failed: pnpm add peertube-plugin-auth-ldap@0.0.14\nNo version specified for 8.6.9 in \"packageManager\" of package.json\n\n at genericNodeError (node:internal/errors:983:15)\n at wrappedFn (node:internal/errors:537:14)\n at ChildProcess.exithandler (node:child_process:417:12)\n at ChildProcess.emit (node:events:519:28)\n at maybeClose (node:internal/child_process:1101:16)\n at ChildProcess._handle.onexit (node:internal/child_process:304:5)",
"message": "Command failed: pnpm add peertube-plugin-auth-ldap@0.0.14\nNo version specified for 8.6.9 in \"packageManager\" of package.json\n",
"code": 1,
"killed": false,
"signal": null,
"cmd": "pnpm add peertube-plugin-auth-ldap@0.0.14"
},
"stdout": "",
"stderr": "No version specified for 8.6.9 in \"packageManager\" of package.json\n"
}
}
```
[09:57:25]
<artlog> yep
[09:57:57]
<artlog> cd /home/yunohost.app/peertube/storage/plugins/
[09:58:23]
<artlog> npm pkg set packageManager=$(pnpm --version)
[09:59:42]
<freetux> Yep j’avais relancé les autres commandes, c’est tout bon 🙂
[10:00:09]
<freetux> info: Successful installation of plugin peertube-plugin-auth-ldap.
[10:02:01]
<artlog> freetux: un retour ?
[10:02:46]
<freetux> La mise à jour est en cours.
[10:03:15]
<freetux> Encore au backup.
[10:12:10]
<hercut> hello, je continue avec mon histoire de plugin pour freshrss, je ne voudrais pas faire de connerie, etj'aimerai un petit coup de main sur ce que je dois faire exactement
J'ai activé l'extension hier, mais je pense qu'il faut faire un peu plus : https://github.com/featurecreep-cron/freshrss-extensions/tree/main/xExtension-ExtensionManager
Mais il parle de docker, ce qui n'es tpas mon cas normalement.
A la place de docker cp, je fais "mv" ?
[10:12:42]
<captainhonora> Hello!
J'ai un view PC portable sur lequel tourne un server yunohost.
J'ai un nouveau serveur (aussi en x86) qui va le remplacer.
Est-il possible de juste mettre le SSD du portable dans le serveur ou vaut mieux installer yunohost et restore le backup?
[10:27:39]
<tituspijean> ok, sorry for the false lead
[10:28:07]
<tituspijean> it might have been running the initial db preparation
[10:28:17]
<Solrac[m]> Seems so! Its loaded just fine. Thank you c:
[10:28:40]
<tokaparas> i noticed yesterday that i can convert a yunohost dyndns fqdn acc.ynh.fr to a yunohost dyndns sub-domain. is there a guide about this and how to create a wildcard LE certificate for it?
[10:29:04]
<tokaparas> my new yunohost dynsdns entry is gonic.acc.ynh.fr
[10:29:18]
<darfeld> Hello there
[10:29:35]
<darfeld> I got a problem with peertube : the app was uninstalled (I guess after an unsuccessful update) and fails to install. ( here is the log https://paste.yunohost.org/raw/henulatore )
Yunohost is installed on debian in an ovh vps.
[11:15:43]
<freetux> Les mêmes qu’avant :
```
2026-05-24 16:47:05,599: DEBUG - {
2026-05-24 16:47:05,599: DEBUG - err: Error: Command failed: pnpm add peertube-plugin-auth-ldap@0.0.14
2026-05-24 16:47:05,599: DEBUG -
2026-05-24 16:47:05,599: DEBUG - at genericNodeError (node:internal/errors:985:15)
2026-05-24 16:47:05,599: DEBUG - at wrappedFn (node:internal/errors:539:14)
2026-05-24 16:47:05,599: DEBUG - at ChildProcess.exithandler (node:child_process:417:12)
2026-05-24 16:47:05,599: DEBUG - at ChildProcess.emit (node:events:509:28)
2026-05-24 16:47:05,599: DEBUG - at maybeClose (node:internal/child_process:1124:16)
2026-05-24 16:47:05,599: DEBUG - at ChildProcess._handle.onexit (node:internal/child_process:306:5) {
2026-05-24 16:47:05,599: DEBUG - code: 1,
2026-05-24 16:47:05,599: DEBUG - killed: false,
2026-05-24 16:47:05,599: DEBUG - signal: null,
2026-05-24 16:47:05,599: DEBUG - cmd: 'pnpm add peertube-plugin-auth-ldap@0.0.14'
2026-05-24 16:47:05,599: DEBUG - },
2026-05-24 16:47:05,599: DEBUG - stdout: '[ERR_PNPM_UNEXPECTED_STORE] Unexpected store location\n' +
2026-05-24 16:47:05,599: DEBUG - '\n' +
2026-05-24 16:47:05,599: DEBUG - 'The dependencies at "/home/yunohost.app/peertube/storage/plugins/node_modules" are currently linked from the store at "/var/www/peertube/.local/share/pnpm/store/v10".\n' +
2026-05-24 16:47:05,599: DEBUG - '\n' +
2026-05-24 16:47:05,599: DEBUG - 'pnpm now wants to use the store at "/var/www/peertube/.local/share/pnpm/store/v11" to link dependencies.\n' +
2026-05-24 16:47:05,599: DEBUG - '\n' +
2026-05-24 16:47:05,600: DEBUG - 'If you want to use the new store location, reinstall your dependencies with "pnpm install".\n' +
2026-05-24 16:47:05,600: DEBUG - '\n' +
2026-05-24 16:47:05,600: DEBUG - 'You may change the global store location by running "pnpm config set store-dir <dir> --global".\n' +
2026-05-24 16:47:05,600: DEBUG - '(This error may happen if the node_modules was installed with a different major version of pnpm)\n',
2026-05-24 16:47:05,600: DEBUG - stderr: ''
2026-05-24 16:47:05,600: DEBUG - }
```
[11:15:52]
<captainhonora> Ah justement je cherche cette page dans la doc. Comment on apelle ce procédé de changer de hardware? "migration" ?
[11:15:57]
<artlogmatrix> https://doc.yunohost.org/fr/admin/backups/migrate_or_merge_servers ?
[11:16:00]
<artlogmatrix> Je suppose que tout a rollbacké automatiquement ?
[11:16:02]
<freetux> Ouais ^^
[11:16:06]
<artlogmatrix> normalemetn on lui a dit dans package.json : voici la bonne version de pnpm , c'est peut être que ce package.json est modifié ... mais comme il a rollbacké on peut difficlemetn regarder
[11:16:08]
<artlog> je ne peux pas reproduire ton problème, toutes mes install on la v11 pur le pnpm store des plugins
[11:16:16]
<artlog> ce qui va peut ẽtre devenir un problème plus tard d'ailleurs ...
[11:16:21]
<captainhonora> super merci
[12:31:16]
<hercut> quelle serait la commande equivalent sur yunohost pour faire ca :
services:
freshrss:
volumes:
- ./freshrss-extensions:/var/www/FreshRSS/extensions
[14:38:13]
<Chatpitaine Caverne> J'avais fait une PR pour compléter cette page. Cette PR n'est pas passée, peut-être avais-je commis une erreur ou bien elle n'est pas correcte, je ne sais pas. Au cas où cela vous serait utile, voici le texte au format brut :
```
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
title: Migrate or merge servers
Migrate a server
If YunoHost's archive system is not convenient enough to migrate a server, you can also migrate from server to server with rsync.
The Yunohost archive system migration consist in :
Preparing a check-list can help
Install Yunohost on your new server (see) The next steps can be done or via web interface or via CLI commands
Proceed to an upgrade of the newly installed server
Restore the system .tar(.gz) archive(s)
Restore the applications .tar(.gz) archive(s)
Processus en GUI :
If you want to use the Web Interface then, you'll have to proceed to Post Installation. Choose the same main domain and the same first user as in your source server.
Proceed to a system updgrade.
Place your .tar(.gz) archives in the folder : /home/yunohost.backup/archives/
Go in the Backup menu, select the archive conresponding to the system backup and restore it. You should find back all your users, groups, domains, certs, ...
Then select the archive(s) corresponding to your applications and restore them (one by one recommended).
You should be good to go.
Processus en CLI:
You don't need to do the postinstall.
Proceed to a system updgrade via sudo apt update && sudo apt upgrade
Go in the folder containing the archives.
Restore the system part by sudo yunohost backup restore Archive_containing_the_system_backup.tar --system
Restore the applications by sudo yunohost backup restore Archive_containing_the_apps_backup.tar --apps (If you want to restore app by app, just add the app Id after --apps)
You should be good to go.
Merge 2 YunoHost servers
If you merge 2 servers together, you will need to recreate the users, domains and permissions of the first server on the destination server. Then you can restore app by app.
:::danger There is a limitation concerning apps that have the same ID. It will not be possible to restore them easily. Also be careful not to delete the eponymous app from the destination server :/ :::
```
[19:50:00]
<stereo> hi, someone here with glitchsoc? i get an error if someone tries to create a new account. i dont see anything special in the logs. put log_level=debug in the .env.production
[19:50:01]
<Thomas> > <@stereo:gnubox.club> hi, someone here with glitchsoc? i get an error if someone tries to create a new account. i dont see anything special in the logs. put log_level=debug in the .env.production
Did you restart the glitchsoc services after the change?