I made a fix to a nextcloud app from the github page, i followed the steps to build from source after i made my change. the result of that built all of the files in the same folder as the source files. my changes worked after i rsynced everything to my apps folder, but i dont want to have all of the source files in the apps folder, it just seems messy. is there a way to specify an “output” location from the npm build command?
the steps to build the app were just
composer install
npm ci
npm run build
it looks like there should be some config in the webpack config js but im not seeing what im expecting
or am i perhaps over thinking this and having the entire source located there in the app folder is ok? i could just git clone into that app folder, make my changes, compile it and then its fine?
You could keep the sources there, in case you wanted to change things later on.
In most apps, there is a Makefile. There is typically a target appstore . This will build and create a .tar.gz or .zip that you can install as normal. No cluttering, this is just how the app is actually deployed.
I cannot check if this is present in the app in question but the boilerplate code contains this target. So, it might be worth looking at this.
Maybe even better would be to open a PR and try to get the changed merged upstream. Then, all users can benefit from your effort.
Chris
Thank you, this is with the calendar app and is probably my own lack of experience building nextcloud apps and it may already be set that way but ill check that out.
They are using krankerl. See the CI workflow for the deployment to the app store.
1 Like