Usually in the observability space it is primarily based on the volume of data and sometimes seat count. Especially if it's freemium like elastic where users can get an idea of volume by running a POC of the free version. Companies do this because of small teams who deploy large infra that would make contracts unprofitable
tiny
You can edit the /etc/fstab or setup systemd mounts so all the files are mounted at the correct spot at startup. Different drives are mounted to folders on Linux instead of drive letters like on windows. Before you reboot, make sure everything works by running mount -a otherwise you will have to rescue the system
If your Linux distro is using btrfs you can format it to btrfs and use btrfs send for backups. Otherwise the filesystem shouldn't be to big if a deal unless you want to restore files from a Windows machine. If that is the case use ntfs
- Aether
- The Absence
- Fox Lake
- Paleface Swiss
Pics or it didn't happen
I fail to see how that differs from the current Internet
Different distros build their packages with different options and have different versions of those packages so the Ubuntu and fedora php packages might have an optimization the arch one didn't
Seafile or nextcloud are my choices. I like seafile because it has an official and documented way to install it but nextcloud works well too just installing it can be tricky. One thing I like about sea file is they have a remote filesystem app that supports Linux and works better than nextcloud and webdav
Devs understand http and json way better than imap and http can support modern security protocols like oidc which standards imap doesn't support which can make using foss email in a corporate environment
Debian testing or nixos
I want to try alpine out but the lack of systemd support is a blocker since I don't want to add openrc support to all my Ansible playbooks that rely on systemd services and timers