MoogleMaestro

joined 1 month ago
[โ€“] [email protected] 1 points 1 week ago

Yeah, thanks for sharing this. I'm going to have to give this a try sometime.

I had previously been building it manually, but I think I'm starting to realize that gitlab/github CI is basically essential to running a proper repository anyway.

[โ€“] [email protected] 6 points 1 week ago

I hate writing a serialized format

I mean, that's why it's serialized. It's not supposed to be written by hand, that's why you have a deserializer. ๐Ÿคฆ

 

I was curious if anyone has any advice on the following:

I have a home server that is always accessed by my main computer for various reasons. I would love to make it so that my locally hosted Gitea could run actions to build local forks of certain applications, and then, on success, trigger Flatpak to build my local fork(s) of certain programs once a month and host those applications (for local use only) on my home server for other computers on my home network to install. I'm thinking mostly like development branches of certain applications, experimental applications, and miscellaneous GUI applications that I've made but infrequently update and want a runnable instance available in case I redo it.

Anybody have any advice or ideas on how to achieve this? Is there a way to make a flatpak repository via a docker image that tries to build certain flatpak repositories on request via a local network? Additionally, if that isn't a known thing, does anyone have any experience hosting flatpak repositories on a local-network server? Or is there a good reason to not do this?

[โ€“] [email protected] 3 points 2 weeks ago (2 children)

I mean, yes. But also no, it sort of depends.

If you have very low bar of needs (needing a web browser and some utility apps, without specific apps in mind) then it's actually never been easier. If you use a Silverblue based system, all updates are done in a transactional way and old versions can be booted into at any time in case something breaks (which basically never happens with silverblue, with some exceptions.) Read only systems means you can't muck around with the root files and can't accidentally "break" your system in the way you used to be able to on older OS designs. I would say that "Linux with Guardrails" is effectively invincible, and I would like to recommend that new users try OSTree based systems. For example, Fedora Silverblue, Ublue's Aurora / Bluefin, Bazzite (Steam OS clone), etc etc.

If you have more specific needs, it can be a crapshoot depending on whether or not the hobby in question has a strong linux presence. Particularly, bespoke non-game windows apps are still a bit tricky to get working and require some Wine (Windows process wrapper for compatibility) knowledge. There are edge cases where running certain applications in flatpak (Steam, Bitwig) can mean that, while it's impossible for these applications to break your system, you'll be very limited in options for these programs. For Steam, this can mean more difficulty with out-of-steam application management. For Bitwig, this can mean no choice in VST. These are all programs that have work arounds, but on a read-only system like Silverblue (which I would like to recommend for new users due to the indestructibility) those are all a little more difficult to implement and require you to know a thing or two about virtual desktops. (Thus, not new user friendly.)

I would still say that it's never been easier, but as you get more famililar with any system, you generally demand more and more from it. Thankfully, with linux, its always been a case of "if there's a will there's a way" and the UX utility applications being made by other people have been getting better and better.

My recommendation to you would be to try UBlue Aurora. It's familiar to Windows, it's being managed in a way that makes gaming relatively simple, and it has an active discord community to help new users. It also has that indestructability that I was talking about before, but has a lot of the "work arounds" pre-setup for new users.

[โ€“] [email protected] 3 points 4 weeks ago* (last edited 4 weeks ago)

I would use BTRFS and Snapper over using Timeshift due to the lack of granularity it has. You should be able to back up any volume you want, not just the home directories like Timeshift does.

[โ€“] [email protected] 8 points 1 month ago (3 children)

Some applications, such as those with tablet demands, are not met by current wayland des with proper tablet support and xwayland is currently the better option. This may have changed in the last year or so, but this is roughly my recollection of certain big art programs.

[โ€“] [email protected] 1 points 1 month ago

I'm currently using debian with Docker.

If I were to do it again, though, I'd probably just use either fedora or the server equivalent to silverblue (I can't remember the name). I am so heavy on docker use at this point that I wouldn't mind going full immutable.

[โ€“] [email protected] 10 points 1 month ago (1 children)

I use BTRFS for the snapshot and subvolume tools.

It is pretty good but usability is a mixed bag. Always getting better by the month though, it feels like.