I just put it in startingpoint since that is what i was using
I just put it in startingpoint since that is what i was using
RI think I want to make an image with wezterm built in to it haha
Rit's a pity helix editor isn't packaged in an official rpm
AHere is the link to your ticket, for anyone reading:
https://github.com/ublue-os/startingpoint/issues/75
https://github.com/ublue-os/startingpoint/issues/75
GitHub
$ rpm-ostree upgrade note: automatic updates (stage) are enabled Pulling manifest: ostree-unverified-image:docker://ghcr.io/noahdotpy/myublue-gnome:latest Staging deployment... done error: Cleaning...
AThis doesn't appear to be any issue caused by uBlue. Have you tried googling that error message? Other ostree users may have encountered it.
AMaking custom images is very easy. I could guide you through it. But I thought wezterm was already on Flathub...
The link is https://flathub.org/apps/org.wezfurlong.wezterm
The link is https://flathub.org/apps/org.wezfurlong.wezterm
Flathub
A GPU-accelerated cross-platform terminal emulator and multiplexer
A@hermmm Were you watching Eurovision yesterday in the tub? I heard Sweden beat Finland. 
AFinland's song was really funny though. It should have won.
AYou can make a distrobox with Arch, install it from AUR and then export it to the host.
XYeah. I read on reddit that we got 84% of the popular vote though, so I'm just sayin fuck the jury and we won.
XIt's a shame Loreen got a win a second time with a much worse song.
XIg they want Eurovision in Sweden next year as it's also Abba's 50 year anniversary.
RI think I saw @j0rge do that in one of his videos 
Rit's on there, but the website will tell you it's only intended for people to have a first loo, because it doesn't allow some of the configuration
R
RSee the note on that section
RThe flatpak is provided primarily for ease of trying out wezterm with low commitment, and you are encouraged to use native packages for your system once you're ready to get the most out of wezterm.
AI agree, Loreen's song is the typical bland modern pop stuff. Your song was hilarious. And it won the people's vote. 
AOh okay, but perhaps they're talking about some rare functionality that you aren't using. Try it and see if it works. 
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call to spawn a shell that runs entirely unsandboxed. While the terminal GUI itself is sandboxed. So most terminals work perfectly in Flathub. If you really need it natively then I can help you get started with making a custom uBlue OS.
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call to spawn a shell that runs entirely unsandboxed. While the terminal GUI itself is sandboxed. So most terminals work perfectly in Flathub. If you really need it natively then I can help you get started with making a custom uBlue OS.RWez does build rpms for each release hosted on GitHub, so I could just cheat by layering it. But since I am considering a build for work focused use with some other things, it wouldn't hurt to include Wezterm
RI asked about the packages on Matrix and a few minutes later he'd replaced Fedora35 with Fedora38 
AIf you're interested, GitHub (Microsoft) will build your OS images daily according to your specification and host it for free on the same container registry that uBlue uses. It involves forking https://github.com/ublue-os/startingpoint on GitHub, then set https://github.com/Arcitec/os/tree/firstboot-refactor as an extra remote and pull all of its changes (they'll be in the main repo later but for now you gotta do it manually). Edit: Those changes are merged so you only need the main repo now.
After you have that, I suggest creating a new branch called something unique, like , set that as your main branch in GitHub's repo settings.
Now just start editing to list the packages you want to include/exclude, and editing to configure your own "on-login package installer".
After you have that, I suggest creating a new branch called something unique, like , set that as your main branch in GitHub's repo settings.
Now just start editing to list the packages you want to include/exclude, and editing to configure your own "on-login package installer".
ROh, one thing I haven't tested on my uBlue install on my laptop earlier was the YubiKeys and U2F working for things like GDM and sudo. Does anyone use that?
AThe reason for branching is so that you can easily fast-forward to upstream anytime, and then rebase your own branch onto main peridically to get improvements.
RI think I saw some rules added to support it, but I haven't tested
AYeah there's device rules installed for that but I don't use it personally
Jyou can also just add it as your day to day terminal but leave the stock terminal there
JI use gnome-terminal as my host
Jand then blackbox flatpak for distroboxes
Rwe do have Enterprise account for work, so we could always run it under our own if we really had to. But making it available would also be useful
XAfter you have that, I suggest creating a new branch called something unique, like , set that as your main branch in GitHub's repo settings.
Here's a job for you: write down the reasoning and instructions for that (and related activities) and PR on the website.
AFor uBlue's website or for startingpoint's readme?
XDidn't think of that. I've been using git merge commits with manual merges to handle getting updates.
AHehe. It's easier to rebase between branches yeah.
AYou can definitely self-host the build and container images, but it requires changing the directory's workflow actions to something you self host.
XThe docs website, yes. The page make-your-own (or whatever) has more general instructions for creating custom images and all the repo setup stuff. Startingpoint's readme is more about startingpoint's configuration.
RRebase with fast forward is really useful for forks 
AYeah, sounds good. I'll add it to my todos and can add do that sometime next week.
Rthat's also something we do for a few public GitHub Actions already. Having an Action to update Action versions 
AHehe. I have been thinking of self-hosting uBlue too. But GitHub doesn't seem to mind hosting 90 days of <large> container revisions for now.
AThere is also an option to pay for GHCR (Github) which doesn't sound too bad if they start charging for the storage. It will probably remain cheap if they decide to add a fee.
Jublue-os/forge is a self hosting setup, more eyes there appreciated!
AI had totally forgotten about forge! It's a very smart idea, to have an easy selfhost process. I guess GHCR is too easy to use to pass up now though.
AI use it for gpg/u2f/webthn and it works fine
Ahaven't done the work to integrate it into pam
Ait should work the same as regular fedora tho https://docs.fedoraproject.org/en-US/quick-docs/using-yubikeys/
X
Bi add wezterm to my custom images... not proposing you use my image, but i've got a helper script to make it easier to install an RPM direct from a github releases page
https://github.com/bsherman/ublue-custom/blob/main/Containerfile#L27
https://github.com/bsherman/ublue-custom/blob/main/Containerfile#L27
AThat's a really nice initiative. Too bad that there isn't an easy way to make CSS / div grids in markdown, so that we could generate that entirely in HTML...
Too bad that there isn't an easy way to make CSS / div grids in markdown, so that we could generate that entirely in HTML...
AHah that's a very nice idea! Thanks for sharing! https://github.com/bsherman/ublue-custom/blob/main/github-release-install.sh
Thanks for sharing! https://github.com/bsherman/ublue-custom/blob/main/github-release-install.shXWell you can use just plain html in markdown, but it's not nice. And extending MkDocs would probably be possible too.