Updates to build service
-
@yusf Don't even need buildbot anymore (architecturally). We integrated docker based images into the platform proper. https://cloudron.io/documentation/custom-apps/tutorial/ (It's all part of 4.3 which is mostly rolled out now, will make release announcement tomorrow).
-
@yusf The build service app claims it might remove docker images in use by other apps so be careful - otherwise I've been using the same install method since I started using cloudron - looks like the process is the same, and they also streamlined it some which is great as well!
-
This post is deleted!
-
@yusf Correct, it is best to run the build service app in a separate cloudron. Essentially, the build service is building a lot of docker images. It "cleans up" old images periodically. For both of these operations, it requires full access to docker. There is a chance that it removes containers/images of the other apps on Cloudron by mistake. As in, this would be a bug but if someone hits that bug on a production Cloudron that would be a disaster. This is the reason why we recommend running it on a separate Cloudron.
Finally, the build service app is not required at all. You can just build and push images from your laptop or a linux VM or some VPS which has docker.
-
Using this app / build service on a local Cloudron instance - is there a way to take the
push
out of thecloudron build
aspect of this since it's all local. Would save a lot of time when developing locally (if it's even feasible, I don't understand the purpose of thepush
part tbh). -
@MooCloud_Matt setting that up would be a nice how-to writeup for all the folks that want to try installing packaged apps not yet in the app store.