Yeah it’s a normal model, but BitWarden is a bit special in that their original server-side implementation was enough of a pain to self-host on a small scale that an alternative implementation Vautlwarden was created. And Vaultwarden became very popular in self-hosted circles. And now many years later BitWarden offers a Lite server which scales down. I think it’s a good thing, just a bit unusual. I’m struggling to think of similar examples.

I’m sure Vaultwarden still funnels plenty of enterprise use of BitWarden, since Vaultwarden users still use official BitWarden client.

Forward thinking venture capital funded companies are getting rarer, hence the question on motivation. Especially the last few years many VC Foss companies have squeezed harder the other way (gitea, Terraform, docker). So all kudos to BitWarden for launching Lite.

What you say a about brand dominance, or brand protection makes a lot of sense. It’s not a good look for them that a large number of people choose to use an unofficial implementation instead of theirs. And should there ever be a catastrophic security issue with Vaultwarden, it would still reflect bad on BitWarden as that kind of nuance (like “unofficial server side implementation”) tend to get lost in reporting. Having more IT workers self-host official version probably also helps pave the way for bringing enterprise-bitwarden to companies.

Valve are a bit of a unicorn though, because they are privately owned. There’s no investors demanding ROI the next quarter, which gives them freedom to think long term.
When Microsoft launched windows8 and the Microsoft Store, Valve took that as an existential threat to their whole business model (the Steam store). Valve feared that Microsoft was trying to position itself like Apple on iOS and Google on Android, where there is only one platform store, and all apps are purchased through the platform store, and the platform store takes that sweet sweet 30% cut. So Valve pivoted to ensure the Steam store would not be obsolete, and give customers a reason to still use the Steam store. And what they achieved is awesome, for Linux, for Valve and for gamers. But it took nearly a decade, which is a level of patience few companies have.

I had the same happen on the root folder on a SATA SSD. The SSD was dying (don’t remember if there was SMART errors, but the dmesg log showed write-errors. I cloned old SSD to a new SSD and haven’t seen the problem since. That was years ago.

When there are multiple consecutive write errors, Linux will re-moumt the partition as read-only to protect the data. (There usually a statement along the lines of “on-error:remount-ro” for the partition in the /etc/fstab file)

Wonder what’s the reasoning behind offering this Lite version. I don’t imagine competing with Vaultwarden is very lucrative financially.

To be honest I don’t remember why I set up gitea with MySQL instead of sqlite (or MariaDB), its quite a few years ago. And sqlite would probably be fine for my single-user instance

I just did it not long a ago. Gittea -> Forgejo10 -> Forgejo11 LTS, in Docker. Surprisingly quick, painless and smooth.

(My only issue was not Forgejo, but MySQL. Because the hardware is ancient and Docker compose pulled down a new version of mysql8 at the same time as pulling forgejo. New version of mysql8 didnt support my CPU architecture. Easy fix was to change the label mysql8oraclelinux7 in Docker compose and pull that image. There is a issue with solutions in the MySQL Docker GitHub repo)

Can attest that Folder Sync is excellent. I use it all day (in the background) for two-way sync (notes) and backup of photos videos etc

Though a small PSA on setting up:
I once set up a new share on a new phone with two-way sync, and the app decided to sync the (newer) empty directory to the server (i.e. delete everything) instead of pulling the files from the server to the phone.
Easy fix: Restore notes from backup (step 0: have backups in the first place), then do an initial 1-way sync from server to phone, then change the sync job to two-way.

AMD already spent a significant amount of effort implementing HDMI2.1 in their open driver in such a way that it would be compliment. The suits from HDMI consortium still said No.

https://www.phoronix.com/news/HDMI-2.1-OSS-Rejected

AMD Linux engineers have spent months working with their legal team and evaluating all HDMI features to determine if/how they can be exposed in their open-source driver. AMD had code working internally and then the past few months were waiting on approval from the HDMI Forum… Sadly, the HDMI Forum has turned down AMD’s request for open-source driver support.

AMD Linux engineer Alex Deucher commented on the ticket:

"The HDMI Forum has rejected our proposal unfortunately. At this time an open source HDMI 2.1 implementation is not possible without running afoul of the HDMI Forum requirements."

There’s nothing wrong with Mint, it’s solid. If it works for you don’t stress about it

The only thing is that it’s based on Ubuntu LTS so it’s packages can be a bit old. Doesn’t really matter much unless you have very new hardware and need the hardware support. Then something Fedora based like Bazzite would be better.

For getting newer software you can use flatpak/Flathub.

Bazzite is also “immutable” which makes it harder to break on a system level, but also harder to tinker on a system level. Mint is a “normal” distribution in that regard. Mint does have Timeshift for taking system level snapshots, on the off chance that an update or your tinkering breaks something. Its worth checking that Timeshift is set up for automatic snapshots

LTS gang rise up ^^

Well today I learned.
I didn’t think “third party” like homebrew would be preferred over ostree-rpm, but makes sense that you shouldn’t change too much from the tested main image.

For anybody else, here’s the exact caveats with rpm-ostree: https://docs.bazzite.gg/Installing_and_Managing_Software/rpm-ostree/#major-caveats-using-rpm-ostree

Personally I mainly used it for fcitx5 language input method some years ago, but I see now that fcitx5 is included in Bazzite, and also that it should work as a flatpak or in distrobox, https://github.com/ublue-os/bazzite/issues/2996

Do you happen to dual boot to Windows when at school, and live 8 timezones from Britain? Linux by default stores the hardware clock in UTC (and concerts to local time on the fly), while Windows stores the hardware clock in local time.

Do you version your compose files in git? If so, how does that work with the dockGE workflow?

I highly recommend you use Proxmox as the base OS. Proxmox makes it easy to spin up virtual machines, and easy to back up and revert to backups. So you’re free to play around and try stupid stuff. If you break something in your VM, just restore a backup.

In addition to virtual machines, Proxmox also does “LXC containers” , which are system level containers. They are basically a very light weight virtual machine, with some caveats like running the same kernel as the host.

Most self-hosting software is released as a docker-image. Docker is application level containers, meaning only the bare minimum to run the application is included. You don’t enter a docker container to update packages, instead you pull down a new version of the image from the author.

There are 3 ways to run docker on Proxmox:

• Install docker inside a virtual machine (recommended).
• Install docker inside a LXC Containers (not recommended because of various edge cases)
• Install docker directly on the Proxmox host (not recommended for various reasons).
• (There is ongoing work for running docker images directly in Proxmox, this is in beta/preview since Proxmox 9.1).

The “overhead” of running docker inside a VM on the host is so negligible, you don’t need to worry about it.

I had never heard of dockge before, but this sounds like the killer feature for me:

File based structure - Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands

Does that mean I can just point it at my existing docker compose files?
My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.
I have portainer, but rarely use it , and won’t let it manage the configuration, because that interfered with versioning the config in git.

For keyboard, if you’re still having trouble, you can try connecting from the terminal with the command bluetoothctl . Terminal commands often tell you more details than GUIs about why things failed.

Regarding distributions, you are on Bazzite, which is an immutable distribution, meaning the root file system is read-only. That makes it a bit different from “normal” distribution. The upshot is that most things should just work and the system is harder to break. The downside is that you sometimes have to jump through more hoops and do things differently from “normal” distributions when you want to do some deeper level tinkering.

If you search for “How to do X in Bazzite” you might get fewer results because Bazzite is relatively new and niche (though growing quickly).
If you search for “How to do X on Linux” you might find that the steps don’t work because you’re root filesystem is read-only.
So sometimes you need to search for “How to do X on Silverblue” , because Bazzite is (sort of) based on Fedora Silverblue, which is the immutable version of Fedora distribution.

If you want to install some software that you can’t find in the app store (Flathub) or as AppImage, your next step is to look up the command rpm-ostree. It layers new software on top of your read-only root system. Changes from rpm-ostre take effect on the next reboot

The arch wiki is indeed excellent

It can get very in-depth though, sometimes more so than you need when just starting out learning Linux. So try not to get overwhelmed by it, OP :)

Also OP, since you’re on Bazzite, you should know that that Bazzite is an immutable distribution, meaning your root file system is read-only. So some of the “advanced tinkering” with system files from arch wiki or random forum posts won’t work the same way.

Improvements for Input devices (particularly stylus and drawing tablets, but any kind of input) is one of the 3 overarching “goals” of KDE at the moment

The article introduction is gold:

In the unlikely case that you have very little RAM and a surplus of video RAM, you can use the latter as swap.

Also its probably a lot easier to handle for performing testing on equal conditions through the tests for all their cards. Sounds like ideally they want to freeze all their versions for at least a quarter of a year or more