What is the "desired" way to update frontend assets with this setup?

[func0der]

hey there.

I can not properly figure this out.
I could not use node in the docker container of server:

> npm install
....
npm ERR! path /var/www/html/node_modules/puppeteer
npm ERR! command failed
npm ERR! command sh -c -- node install.js

nor could I just build, because:

> npm run build

> nextcloud@1.0.0 build
> NODE_ENV=production webpack --progress --config webpack.prod.js

sh: 1: webpack: Permission denied

What is the "desired" way to do so? Are you supposed to run it on your host machine?

P.S: Thanks for the awesome work :)

[juliushaertl]

I usually run it on the host, but it should not make a difference in general. For the specific issue it seems that the server installation of dependencies fails. Maybe you can try to run PUPPETEER_SKIP_DOWNLOAD=true npm ci instead of npm install and see if that makes a difference.

[func0der]

As far as I understand the JS code has to be 'build' during creation of the docker images or rather their first spin up. Since this is a development environment it would make no sense to have them as part of the images itself.
Do I understand that correctly?

Why not just run that command again? Where would that be? I could not find it.

[juliushaertl]

The frontend code is not built automatically by the container. The developer should be in control when those are built.

For the server itself the js assets are part of the repository which means that there is no need to manually build unless you do changes.

[func0der]

Ah. I am not used to this kind of operation.
I usually use lock files and build pipelines for assets, just like you would do with composer and the vendor folders.
That way the also stay the same for each build as long as you do not touch the source or lock files.

Thanks for the insight.