Closed FredMa01 closed 2 months ago
Thanks for the issue. Is this a bare metal installation? It could be that the files are not created. So for that you just do pnpm i, go to the admin folder in the root directory and do pnpm run build . That should suffice for the templates to be registered.
Thanks ! It's a bare metal installation ( Intel ATOM N2800 - 2c/4t - 1.86 GHz - 4 Go 1066 MHz RAM). The command ''pnpm i'' is very long and saturates the server. She doesn't stop. This explains why she does not go through with the new installation.
Oh yes the old npm modules will be removed. Pnpm is the fastest package manager currently available.
Sorry for posting in a closed issue but as I have the exact same issue that I solved as suggested with pnpm run build
I thought that asking my question here would make sense: is that the default behavior that with an new install or an update from older version, users have to run pnpm run build
?
With the move to React an extra build step is required. I could add that to the installDeps script or is that already present? I could definitely add that to the documentation.
adding that to the documentation would be nice. I don't use the installDeps script as I use ansible role to deploy, should I ?
It normally covers all build steps but seems like this is not included in it. I'll fix that for the next release.
After a new installation today : git clone --branch master https://github.com/ether/etherpad-lite.git etherpad
I have this error : Error: ENOENT: no such file or directory, stat '/home/etherpad/src/templates/admin/index.html
Admin templates disappeared of /scr/templates. Etherpad version is 2.0.1 (4631e14) pnpm --version: 8.15.5 Debian 12