silverblue-akmods-keys VS Visual Studio Code

I'm using Silverblue 39 for about 2 month coming from NixOS Unstable. It's working very well for me. I have some packages layered like Nvidia and fish shell and https://github.com/CheariX/silverblue-akmods-keys for AKMODS modules work with secure boot. Things like neovim, pyright, helix, starship, LSPs and CLI applications I install with brew (brew.sh). For desktop things I use Flatpak.

I had a problem with some Flatpak applications (like Steam and Discord) and brew because brew puts its folder in the $PATH before the default ones (/usr/bin ...) and those Flatpak applications tried to use SSL keys from brew instead of the system ones. I just changed the order of the $PATH to make brew bin path to be after ther system ones.

For VSCode I'm not using the Flatpak I'm using the tarball one I just extract in ~/applications and symlink the code binary in the ~/.local/bin. It's working well, I don't have problem with VSCode not executing LSPs and lint things. The only problem is VSCode from tarball cannot updates itself, so I need to download the newer version and extract to ~/applications. There is this VSCode CLI version (https://code.visualstudio.com/docs/?dv=linux64cli) but I was not able to make it use the wayland backend.

rpm-ostree install --apply-live rpmdevtools akmods sudo kmodgenca sudo mokutil --import /etc/pki/akmods/certs/public_key.der git clone https://github.com/CheariX/silverblue-akmods-keys cd silverblue-akmods-keys sudo bash setup.sh rpm-ostree install akmods-keys-0.0.2-8.fc$(rpm -E %fedora).noarch.rpm

On workstation, no. On Silverblue, yes. There is a package on Github that will help you if you are on Silverblue. Link here: silverblue-akmods-keys

It works, but only with a hack where you manually have to overlay a self build package that provides the akmod keys.

Unfortunately I can't test it, as this feature is currently still broken (workaround) on Kinoite/Silverblue and Silverblue is the only version of Fedora I use.

Kinoite and Silverblue have problems signing akmods, though https://github.com/CheariX/silverblue-akmods-keys is a completely functional workaround. Non-rpm-ostree variants of fedora should work according to what I have seen online.

I'm using Silverblue 39 for about 2 month coming from NixOS Unstable. It's working very well for me. I have some packages layered like Nvidia and fish shell and https://github.com/CheariX/silverblue-akmods-keys for AKMODS modules work with secure boot. Things like neovim, pyright, helix, starship, LSPs and CLI applications I install with brew (brew.sh). For desktop things I use Flatpak.

I had a problem with some Flatpak applications (like Steam and Discord) and brew because brew puts its folder in the $PATH before the default ones (/usr/bin ...) and those Flatpak applications tried to use SSL keys from brew instead of the system ones. I just changed the order of the $PATH to make brew bin path to be after ther system ones.

For VSCode I'm not using the Flatpak I'm using the tarball one I just extract in ~/applications and symlink the code binary in the ~/.local/bin. It's working well, I don't have problem with VSCode not executing LSPs and lint things. The only problem is VSCode from tarball cannot updates itself, so I need to download the newer version and extract to ~/applications. There is this VSCode CLI version (https://code.visualstudio.com/docs/?dv=linux64cli) but I was not able to make it use the wayland backend.

Explore the official VS Code documentation on the Visual Studio Code website for in-depth guides, tutorials, and reference materials.

It's a lot, but the VS Code docs have thought about Extraneous Cognitive Load and created written guides, video guides, reference docs and more!

VSCode has a long history of not working well with Unity, so they deprecated it.

> Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux.