Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
For the isobuilder, I would really suggest that you use the long-form Lorax builder above (the templates are in their repo) rather than mkksiso. This seems like added complexity for no reason, but outside of sucking bandwidth that you're paying for every time someone fetches it from cloudfront, the way it's currently done more or else forces anyone who downloads the ISO to re-fetch the compose, and use more bandwidth, or just outright fail in airgapped environment, and it's sure to make your CI (if you have CI around the ISO) much slower than it needs to besides.
We include a bunch of extra udev rules for controllers and other hardware: That container is here specifically if you want to inspect it: https://github.com/ublue-os/config
And also all the codecs are turned on, here's that container: https://github.com/ublue-os/main
The goals of this project are great, but technically, it's not that difficult. Here's an older repo for a custom-ostree. ostree configs are a list of packages, an optional post-setup script, and some repos.
Yeah! If you take a closer look at our repos three of them are built this way, here's lxqt for example: https://github.com/ublue-os/lxqt
It takes about 40 minutes to build an image that way vs 2 minutes to derive your own, so for us it's easier to build from the existing base images that Fedora provides: https://gitlab.com/fedora/ostree/ci-test - it makes sense for Fedora to build it this way (hyperreal, the vauxite author was able to submit they're work into this repo, which is nice!)
For the isobuilder, I would really suggest that you use the long-form Lorax builder above (the templates are in their repo) rather than mkksiso. This seems like added complexity for no reason, but outside of sucking bandwidth that you're paying for every time someone fetches it from cloudfront, the way it's currently done more or else forces anyone who downloads the ISO to re-fetch the compose, and use more bandwidth, or just outright fail in airgapped environment, and it's sure to make your CI (if you have CI around the ISO) much slower than it needs to besides.