This message was deleted.

Hi @glamorous-toddler-19317, You can refer https://github.com/harvester/ipxe-examples to know how to provision the harvester cluster. The harvester consists of various components, which I recommend you try to use, and you will get more info on this.

Hi @salmon-city-57654 Thank you for this. I indeed am exploring all the components and got curious about how they are merged into an ISO. So far, I learned that the harvester-installer creates the ISO file, but it's not clear how changes to the UI or backend of Harvester are reflected in this build. I have experience in backend and frontend development, so I was exploring those components. Is there any documentation on this? I noticed the build process pulls Harvester images from Docker Hub. How can I test my backend changes and incorporate them into the ISO built by the installer component?

This might help https://github.com/harvester/harvester/wiki/Build-ISO-images 🙂

Hi @ambitious-daybreak-95996 Thanks a lot, will try this right away. This PR is perfectly timed and addressed the issues I was facing with editing the dapper file, something I've been struggling with since yesterday.

I'm not sure exactly how to go about changing the dashboard that's embedded in the ISO, sorry -- see package/Dockerfile in the harvester repo, from about line 31 or so - it's pulling three tarballs of the UI. I suspect you'd need to (somehow) build equivalent tarballs from your version of the dashboard code, then put them somewhere (local web server, whatever) your build can access it), then tweak that Dockerfile to point to your version. I don't know if there's a better way to do this, as I haven't really looked at it.

Just checkout that particular Docker file. I too believe, those tarballs might be the solution. looking into it. Thanks for your time :)

no problem, hope it works!