I have a number of questions regarding the building / deploying a release.
When I use
balena deploy myApp --logs --source --build ., it says it’s up to date. However, I’ve changed things in my Node.js project. So it would be weird if it’s already built. (balena cli v12.5.0, multi-container app, raspberrypi4 application). Even using the
--buildoption, doesn’t trigger a new build.
When I’m building my app using
balena build --application myApp --logs --source --build .on my desktop, the building process takes a really long time. It has to compile some things for Node.js (like the sqlite3 module), but will performance increase when I use a Raspberry Pi 4 with Raspbian and Docker? So create a dedicated builder for the Raspberry Pi 4 app?
When I use
balena push <local-ip>, it takes quite some time to start building, like a few minutes. That’s before it starts building (so the yellow warning shows up, but then halts). After those few minutes, it starts to build, which is quite fast. My Node.js app is in Typescript, so I have to build before I push. So I can’t use livepush. I can be wrong, but it never took so long to start building in my experience. Is something changed there? (balena cli 12.5.0, balenaOS 2.48.0+rev1)
balena push <local-ip>, where does the build take place? On the device or on my PC? And if it’s on my PC, why is that faster than using
Thanks in advance for clearing this up