It’s been a while since I last did this. Let’s try this one instead:
sudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
1 Like
Edited my post while you were replying 
It’s installing now. Thanks!
1 Like
I must say - the install of -gts was silky smooth.
Layered 1Password, ujust brew, ujust zsh, then brewed my command line commands like neovim, chezmoi, ripgrep, fd, zoxide, etc.
Installed flathub stuff.
Everything just works.
Kudos to the team!
4 Likes
That’s was great presentation @j0rge .
I’ve been using bluefin-dx since Jan on my Framework (11th gen).
Things seems to have changed a lot in those 3 months , so, I do have some questions:
-
just vs ujust
When I installed back then, I don’t remember ujust existing… That’s the new way to install things instead of using just directly ? -
is fleek/nix still something you plan to move forward?
When I installed dx, there was the option of using fleek/nix-global as a way to install cli besides brew. I was using home-manager + Silverblue before moving into bluefin, so I have it a try (as a more digestable way to handle my home instead of nix files).
It seems that this path disapeared from the documentation , so , I wanted to know if this was taken out of the ‘paved road’.
I ask because it seems clear to me that the focus now is brew … and I do remember that fleek had support for it. -
It seems the power manager did change. I do remember right, the framework image I installed back then (January) was using TLP … Is this new power manager as good as that ? As all upgrades happen “under the hook”… does that mean that my laptop possibly also moved into that new power manager ?
-
this one is more as a curiosity: brew x nix ?
I don’t wanna start any war
, but, all things considered, a nix-global setup has the same usability of brew . Does brew have more packages the nix, and , is that in general more up to date ?
I do use brew at my company laptop (mac) and nix in my personal laptop (framework+bluefin) and I don’t see much diference for what I used up to now.
So, I would like to understand the preference for brew. -
shared home dir compatibility problems
as the home dir is shared between all containers, and anything installed on host, isn’t the use of the same dotfiles .config and .cache folders a potencial compatibility problem between several diferent versions of the same apps ? -
how to bring my current install to the new preferences and tools?
as mentioned, I do have an install running since january, and it seems my install is missing things like the logo menu and boxbudy -
final one: silent upgrades
I understant that all upgrades happen silently under the hood. Maybe I’m old fashioned, but I really dislike shutting down my laptop unless strictly necessary. Would you find a “the following upgrades were made and will be applied on reboot” to disturbing ? I find it hard to track what is being upgraded on my machine.
Sorry for the wall of text , you guys are making some amazing work with bluefin 
1 Like
ujust is basically just with /usr/share/ublue-os/justfile as the default recipie file. I believe the “u” stands for “universal” from “universal blue”
I’m no nix expert, but you can use both, because nix (the package manager) is usable on all Linux systems. The cli of brew is easier to learn though.
yes
You should be able to turn them on in the extensions manager. Doing a dconf reset will reset your desktop to the defaults, but that will also blow away your custom keyboard shortcuts so ymmv on this one.
ujust changelogs is the best thing we have for this right now.
Any way to install homebrew on the Bazzite host?
We’re working on just moving the brew stuff to config so it’s in every ublue image (including bazzite), for sure we’ll get to it before F40 releases.
2 Likes
Yes.
brew works perfectly!
The fourth leg in the framework that allows to install software in an immutable OS.
How could we look under the hood in ujust brew?
I would like to know the raw commands that make the installation of brew possible.
Here’s the pull request:
1 Like
I have a relatively newbie question. I launched Bluefin-cli, I prefer to jump in the deep end and figure it out-eventually, I use OBS-studio to train my clients on Zoom and rely on VirtualCam. My question is, when usine Bluefin-cli the VirtualCam button disappears, which I assume is because I’m now in the container, how do I link it Bluefin-cli to be able to use it again for work?
Currently v4l2loopback is not building on Fedora 38 and 39 which is what obs uses for virtual camera.
I haven’t switched to the latest Bluefin yet and so haven’t run the bluefin-cli container or boxbuddy yet, but what i have been doing is setting up my distroboxes with the --home flag in order to point the container home directory to something specific for the container.
So I’ll add --home /home/my-normal-user/containers/my-project-xyz-container/ to the distrobox create command. Doing this I’ll have separate home folders for each container which all the dot and config files for that container go into.
Nice to have separate zsh history for each container.
2 Likes
Is the recommended way to install brew in distrobox instead of host? Having more than one pkg managers co-exist seems to cause trouble…
The default experience (the one I use) is brew on the host.
1 Like
There shouldn’t be a problem! Silverblue derivatives are supposed to be hermetic and isolated.
I use brew in the host, LXC, Nix, and distrobox applications with no conflicts so far.
1 Like