Bi ment how come we can now ship them in image i understand the size issue limitations
AIt’s not just about size though, it basically stops updates too as they’re part of the image
AI played with doing that for myself and this was the deal breaker for me at least …
AI guess it’s not that bad for system-level flatpaks 
Abasically
flatpak upgrade
EThat's true. Probably fine for what we ship but still certainly a con
JI'm in san jose and just hung out with Kyle
Jgot to see bazzite on the oled special edition deck, it was glorious!
Jseeing the Prompt terminal on it was icing on the cake, it's going to be an awesome week!
EThat's awesome! Will be giving unl0kr another swing tomorrow
Ris there such thing as https://quay.io/repository/fedora-ostree-desktops/silverblue?tab=info but includes testing repo?
Quay is the best place to build, store, and distribute your containers. Public repositories are always free.
BStarlight from astro is a super-easy way to build docs for a project. https://starlight.astro.build/
Starlight
Starlight helps you build beautiful, high-performance documentation websites with Astro.
Bi put together https://blincus.dev in maybe 30 minutes. Still missing lots of words, but getting all that nice plumbing done in half an hour is a nice bonus.
B(this project is not ready for human consumption, no need to tell me about broken links, etc)
BAstro
How WP Engine, the world’s largest managed WordPress hosting provider, went from spending most of their time managing their content to actually writing it.
XAgreed 100%! Astro is always a blast to use, Starlight makes it quick and easy for docs.
XI'd pick it over MkDocs any day.
FXVue-only though, and I suppose less features since Starlight should inherit all of Astro's features I think.
J@KyleGospo zoom zoom zoom https://gitlab.gnome.org/chergert/prompt/-/commits/main
GitLab
A terminal for a container-oriented desktop
KGitLab
Hi! I'd like to eventually ship this as the default terminal in various ublue projects. For the integration to be seamless and replace gnome-terminal everywhere it's used, we...
J
Boh shoot, this will be awesome
EReplacing GNOME Terminal with Prompt would be wonderful
Jhopefully we'll have a release of it this week!
Jfinally, we're almost done!
K@j0rge he just finished those lmao
EHmm...
error: Could not find installation imageOHHHH missing the conf
K@EyeCantCU see latest testing commit
Kmade a minor change to what you did
ELooks good to me. Wasn't entirely sure what the best placement was but now I understand why that additional copy exists
ENow this is interesting. I wonder when exactly the fedora remote gets added or if it is somewhere else on the image:
error: Remote "fedora" not found in the system (image) installationS-tier!
ESo I understand why now. The remote, Silverblues preinstalled Flatpaks, etc - all get written to a different directory. Because we change where this all gets installed, those those things aren't in the path set by the installation. Might still be a case for a minimal service that runs Fedoras third party opt out and removes the Fedora remote along with the Flatpaks we had been removing from Silverblue in Bazzite. Assuming this route is optimal when it's said and done
ERan out of space again lol
EThis time with the builders
KRip
KThat's with like 40 GB added too
EYeah... Let's not
AGitHub
Tool to compose installer ISOs for OSTree based containers - akdev1l/mkociso
AIt’s not part of the image as that stuff gets written in /var
EYeah. /var/lib/flatpak
ESometimes I get a bit confused lol
EDefinitely the way forward. I want to sit down and work out a working GitHub action
AWe just need to add that Lorax templates and some wiring up to mkociso then the GitHub can do it
AMm I think I can work on this tomorrow
EWould really appreciate that. Will help in any way I can
