aports VS vaultwarden

alpkg is a tool for all your Alpine packaging needs. It can create a chroot with preinstalled tools in a matter of seconds, set up aports repository, and fetch/update packages. Most importantly, it provides a split layout via Zellij for easy editing/building APKBUILD files.

A nice feature of Alpine Linux is that the package repository is a relatively straightforwardly-structured git repository containing build scripts for each package:

https://gitlab.alpinelinux.org/alpine/aports/

It's worth reading the contributor guide[1] before signing up and providing any fixes and improvements - and from there, hopefully it's a relatively familiar workflow for many developers.

[1] - https://wiki.alpinelinux.org/wiki/Alpine_Linux:Contribute

1) docker and qemu (using qemu-user-static) 2) alpine-chroot-install (https://github.com/alpinelinux/alpine-chroot-install/) 3) bootstrap.sh (https://github.com/alpinelinux/aports/blob/master/scripts/bootstrap.sh)

To people who want to self-host this, look at Vaultwarden which is a fully compatible alternate server with even more features:

https://github.com/dani-garcia/vaultwarden

Been running it for a year with 0 issues.

For passwords and 2FA I use Bitwarden in combination with a self-hosted Vaultwarden service (for imcreased security and use of pro features for free).

Vaultwarden as Password-Safe

I have a lot of software that I host myself on my home server, partly to save money but also because I want to control my own data. For example, I host VaultWarden which is the open source server for BitWarden. This gives me all the premium features for free with the added bonus of keeping my passwords out of the cloud.

Self hosting is incredibly easy with vaultwarden (https://github.com/dani-garcia/vaultwarden)

I have now switched to using the BitWarden app with the self-hosted VaultWarden server. I have set it up, so my passwords are only accessible when connected to my home network either physically or with a VPN (I am using tailscale for this).