toolbox-vscode VS keepassxc

This helper script

VSCode + toolbox container + https://github.com/owtaylor/toolbox-vscode.git

Linking VS code with remote development in your container can be achieved very well. I found this repository and the setup is superb! https://github.com/owtaylor/toolbox-vscode

Have a look at this script, which has been made even easier with this.

I use https://github.com/owtaylor/toolbox-vscode, then you can have the vscode frontend in flatpak and the backend (where language servers and compilers run) in a toolbox container

There’s this script, and also this approach to simplify using said script.

Yes sir, you need to use the Remote - Containers extension and this script https://github.com/owtaylor/toolbox-vscode

You can use toolbox-vscode to make the flatpak more useful

KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:

https://github.com/keepassxreboot/keepassxc/pull/8825

If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.

https://keepassxc.org/

That's why you use the superior one, KeePassXC, as linked in the NIST link: https://github.com/keepassxreboot/keepassxc/discussions/9433

Over there, they got pissed about people constantly bugging them about it and closed the bug with the last comment reading:

for the internet, use a password manager like keepassxc with a strong password.

Another regression is that KeePassX/C AutoType doesn't work with Wayland, so now instead of a simple CTRL+V in KeePassXC, I have to separately copy and paste the user and the pass.

https://github.com/keepassxreboot/keepassxc/issues/2281