hmm, not sure why baca would need so many requirements. I installed baca using pip as per (https://github.com/wustho/baca), on a hedless ubuntu based server. Maybe on Arch it would need to install / update python packages?

You could also try epy (https://github.com/wustho/epy) which is also a terminal based epub reader.

baca is a terminal based epub reader. Quite nice.

If you are just looking for a way to SSH into your machines from outside your network, you can setup a more recent VPN or Wireguard yourself. If you have a Raspberry Pi lying around, using PIVPN makes things super easy. You can have both OpenVPN as well as Wireguard running if you want, using the same script. If that is the only thing you like to do, then there is no need to reverse proxy your servers and expose them. Just having a VPN or Wireguard connection should be enough to access your servers when outside of your network. It is recommended to have a fixed IP btw, to find your VPN/Wireguard server easily.

Also, you can leave all your servers locally (and not exposing them) when you can reliably setup a VPN/Wireguard connection. That is the most secure I guess.

you can automate a lot of the basc profile stuff in your dotfiles with some automation such as https://github.com/anishathalye/dotbot to bootstrap a new install. it makes your new distro right at home, and if you combine this with github to store your dotfiles, you’ll also have a backup of your environment.

Does this affect ubuntu and raspberry os releases as well? Since these are based on debian?

Looks like a pretty straightforward install! And a fun project to have a personal message space with friends. It includes the ability to launch gameoso you could maybe set it up as a personal lobby for gaming buddies.

I think you would also need an initial run process such as systemd or the sysV runlevels.

This also looks similar to Tailscale (https://tailscale.com/). I have not used this but saw it popping up in youtube recently.

This I understand, from a user space perspective the Flatpaks seems like a good thing; isolated from the OS. For a server only environment it seems to be less of an issue, provided that the sys admin knows what he/she is doing.

So what is the general consensus on package management these days on Debian based distributions? I may be old school by relying only on APT (DEB) for my Linux machines, and never really got into Snap, Flatpak, and what not. Is APT still most used? Or is there a significant movement towards Snap or something else. What I hated when I looked at Snap the last time is that distributions come with different concurrent architectures on package management, which from a point of view of organizing you system just doesn’t make sense. A difference between package management (APT/Flat/Snap) on the one hand and service management (Docker, k8, …) on the other hand I understand.

Those are some great pickup lines for a big bar on Friday! ;)

Are we sure it is the same thing? Alien-in-the-middle attack succeeded… 😁

There is also a very clear upwards trend I would say 😁

Hosting an email server is pretty sure a magnet for half the Chinese IP range… So I would refrain from hosting that myself.

Unmonitored, it will slowly evolve into V’ger now!

Not sure if it answers your question, but I use Portainer to check the different docker containers I am running. It does not allow me to check the ‘docker-runtime’ logs themselves though, only the logfiles of each of the running containers. It also allows easy term connection if you want, although I usually do that directly form the terminal itself.

Started out with lastpass many years ago, until it was bought by logmein. Have been using Bitwarden since.