2-" error: Error: Command failed: add thread file:/home/ubuntu/peertube-plugin-auth-ldap
warning package.json: No license area
warning No license area
error Package " file:/home/ubuntu/peertube-plugin-auth-ldap " refers to a file that does not exist ’ " file:/home/ubuntu/peertube-plugin-auth-ldap/'" I get the error.
3- How do I edit the" license field" error in the package.json file?
Anyway, the message about the « license » is just a warning. It seems that your trouble orginates from the the path location « /home/ubuntu/… ». Maybe this need to be elsewhere, or to have particular access right (for the user named peertube or other).
Without any internet connection, it will not be simple.
Installing a plugin, event using the CLI, need to download all NPM dependencies.
It might be possible, by using npm install on a computer that has internet, then copy the complete folder on the server (including the node_modules directory).
When I changed the directory, the error changed and became as follows, but it did not work.
(error couldn’t find package « ldapauth-fork@^5.0.0-rc.6 » required by « file :/var/www/peertube/storage/plugins/peertube-plugin-auth-ldap/ » on the "npm " registry.)
I can’t get this solution to work on my environnement.
It certainly comes from something that I don’t understand about npm.
I have build my plugin-auth-ldap archive and copyed it on my offline server. (nodes_modules seems fine and dependances are present inside it)
I am on a docker install, so I mounted the folder inside the container. (Setting up the ownership to peertube user)
But every way I tried to install from inside the container with the provided command « npm run plugin:install — —plugin-path /local/plugin/plugin-auth-ldap » npm tries to get modules from npm official registry and end up failling.
Have you had any progress here? I’m experiencing the same behaviour. I’ve tried both npm run plugin:install and peertube-cli plugins install and they both fail while trying to connect to a npm registry, even though all dependencies should be present after npm ci.