#bluebuild — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #bluebuild, aggregated by home.social.
-
The end of the year is nearing and I've updated my blog with some details on my latest #linux setup #fedora #silverblue #ublue #bluebuild
https://www.davd.io/posts/2025-12-02-my-linux-setup-2025-2026/ -
The end of the year is nearing and I've updated my blog with some details on my latest #linux setup #fedora #silverblue #ublue #bluebuild
https://www.davd.io/posts/2025-12-02-my-linux-setup-2025-2026/ -
The end of the year is nearing and I've updated my blog with some details on my latest #linux setup #fedora #silverblue #ublue #bluebuild
https://www.davd.io/posts/2025-12-02-my-linux-setup-2025-2026/ -
@stoeps Hab grad deinen Vortrag zu Chezmoi und den Hint zu BlueBuild gesehen. Danke dafür! Habe gerade mein Bastel-Setup für mein #Silverblue-Image zu #BlueBuild migriert und das ist gleich viel schöner so! Inkl. First Run Wizard :) Stow -> Chezmoi-Migration kommt als nächstes
-
@stoeps Hab grad deinen Vortrag zu Chezmoi und den Hint zu BlueBuild gesehen. Danke dafür! Habe gerade mein Bastel-Setup für mein #Silverblue-Image zu #BlueBuild migriert und das ist gleich viel schöner so! Inkl. First Run Wizard :) Stow -> Chezmoi-Migration kommt als nächstes
-
@stoeps Hab grad deinen Vortrag zu Chezmoi und den Hint zu BlueBuild gesehen. Danke dafür! Habe gerade mein Bastel-Setup für mein #Silverblue-Image zu #BlueBuild migriert und das ist gleich viel schöner so! Inkl. First Run Wizard :) Stow -> Chezmoi-Migration kommt als nächstes
-
@stoeps Hab grad deinen Vortrag zu Chezmoi und den Hint zu BlueBuild gesehen. Danke dafür! Habe gerade mein Bastel-Setup für mein #Silverblue-Image zu #BlueBuild migriert und das ist gleich viel schöner so! Inkl. First Run Wizard :) Stow -> Chezmoi-Migration kommt als nächstes
-
@stoeps Hab grad deinen Vortrag zu Chezmoi und den Hint zu BlueBuild gesehen. Danke dafür! Habe gerade mein Bastel-Setup für mein #Silverblue-Image zu #BlueBuild migriert und das ist gleich viel schöner so! Inkl. First Run Wizard :) Stow -> Chezmoi-Migration kommt als nächstes
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
3/3 Thanks to the open source communities who helped and developed to the benefit of #EU_OS!
1) #foreman integration with #bootc facts export also for Fedora: https://copr.fedorainfracloud.org/coprs/rriemann/eu-os/package/bootc/
2) #bluebuild improves local deployment of OCI containers for better development https://github.com/blue-build/cli/pull/448
3) #foreman investigation of issues with OCI registry receiving large containers (ours is about 9GiB) https://projects.theforeman.org/issues/38649We got a #Matrix channel for developers at #eu-os-dev:kde.org Come over and say hi!
-
#introduction hiiiiii fedi
just moving my account from @[email protected]
i currently post art on @[email protected]
so this account is mostly meant for more general use (though i do reserve the right to post art here too)topics i might be talking about:
- linux
- my project @bluebuild
- universal blue
- fedora atomic and other next-gen distros
- ui/ux and web dev / design
- generative art
- selfhosting
- whatever else i may tinker with..#fedora #atomic #fedoraAtomic #BlueBuild #ublue #uiux #webdev #generativeart #selfhosting #linux #foss #tech
-
#introduction hiiiiii fedi
just moving my account from @[email protected]
i currently post art on @[email protected]
so this account is mostly meant for more general use (though i do reserve the right to post art here too)topics i might be talking about:
- linux
- my project @bluebuild
- universal blue
- fedora atomic and other next-gen distros
- ui/ux and web dev / design
- generative art
- selfhosting
- whatever else i may tinker with..#fedora #atomic #fedoraAtomic #BlueBuild #ublue #uiux #webdev #generativeart #selfhosting #linux #foss #tech
-
@bluebuild I've tried to join the #matrix channel #bluebuild:matrix.org today, but it did not work. Is there something special about it? Does it still exist?
-
@bluebuild I've tried to join the #matrix channel #bluebuild:matrix.org today, but it did not work. Is there something special about it? Does it still exist?
-
@bluebuild I've tried to join the #matrix channel #bluebuild:matrix.org today, but it did not work. Is there something special about it? Does it still exist?
-
@bluebuild I've tried to join the #matrix channel #bluebuild:matrix.org today, but it did not work. Is there something special about it? Does it still exist?
-
@bluebuild I've tried to join the #matrix channel #bluebuild:matrix.org today, but it did not work. Is there something special about it? Does it still exist?
-
@bluebuild I'd like instructions for how to use #BlueBuild with #Codeberg @Codeberg
-
@bluebuild I'd like instructions for how to use #BlueBuild with #Codeberg @Codeberg
-
@bluebuild I'd like instructions for how to use #BlueBuild with #Codeberg @Codeberg
-
@bluebuild I'd like instructions for how to use #BlueBuild with #Codeberg @Codeberg
-
finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now
that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for
for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests
-
finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now
that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for
for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests
-
finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now
that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for
for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests
-
finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now
that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for
for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests
-
finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now
that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for
for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds
`testing` builds daily + on commits to main (same as before)
`stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily
https://github.com/zelikos/zeliblue/tree/main/.github/workflows
-
did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds
`testing` builds daily + on commits to main (same as before)
`stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily
https://github.com/zelikos/zeliblue/tree/main/.github/workflows
-
did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds
`testing` builds daily + on commits to main (same as before)
`stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily
https://github.com/zelikos/zeliblue/tree/main/.github/workflows
-
did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds
`testing` builds daily + on commits to main (same as before)
`stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily
https://github.com/zelikos/zeliblue/tree/main/.github/workflows
-
did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds
`testing` builds daily + on commits to main (same as before)
`stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily
https://github.com/zelikos/zeliblue/tree/main/.github/workflows
-
ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite
there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: https://github.com/zelikos/zeliblue/pull/256
-
ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite
there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: https://github.com/zelikos/zeliblue/pull/256
-
ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite
there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: https://github.com/zelikos/zeliblue/pull/256
-
ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite
there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: https://github.com/zelikos/zeliblue/pull/256
-
ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite
there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: https://github.com/zelikos/zeliblue/pull/256
-
I've merged my experimental COSMIC image into Zeliblue's main branch
it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR
main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)
-
I've merged my experimental COSMIC image into Zeliblue's main branch
it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR
main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)
-
I've merged my experimental COSMIC image into Zeliblue's main branch
it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR
main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)
-
I've merged my experimental COSMIC image into Zeliblue's main branch
it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR
main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)
-
I've merged my experimental COSMIC image into Zeliblue's main branch
it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR
main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)
-
Here's an awesome, short overview of what Universal Blue, Bluefin, and @bluebuild are! Thanks to @Akzel for putting this together. :)
If you want something short to share with friends as you're trying to explain all this stuff, this video is a nice starting point.
https://www.youtube.com/watch?v=GyMqCZYNPzE#uBlue #Bluefin #BlueBuild #FedoraAtomic #Fedora #Linux #OpenSource #CloudNative