I was asking them to post their setup so I can evaluate their experience with regards to Proxmox and disk usage.

There is no way to get acceptable IOPS out of HDDs within Proxmox. Your IO delay will be insane. You could at best stripe a ton of HDDs but even then one enterprise grade SSD will smoke it as far as performance goes. Post screenshots of your current Proxmox HDD/SSD disk setup with your ZFS pool, services, and IO delay and then we can talk. The difference that enterprise gives you is night and day.

Yes you don’t need Proxmox for what you’re doing.

https://forum.proxmox.com/threads/2-node-cluster-with-the-the-least-amount-of-clusterization-how.140434/#post-628788

https://forum.proxmox.com/threads/consumer-grade-ssds.141190/post-632197

ZFS absolutely does not require them in any way.

Who said it does? Also regarding Proxmox:

https://forum.proxmox.com/threads/2-node-cluster-with-the-the-least-amount-of-clusterization-how.140434/#post-628788

https://forum.proxmox.com/threads/consumer-grade-ssds.141190/post-632197

Looking back at your original post, why are you using Proxmox to begin with for NAS storage??

For ZFS what you want is PLP and high DWPD/TBW. This is what Enterprise SSDs provide. Everything you’ve mentioned so far points to you not needing ZFS so there’s nothing to worry about.

Yes I’m specifically referring to your ZFS pool containing your VMs/LXCs. Enterprise SSDs for that. Get them on ebay. Just do a search on the Proxmox forums for enterprise vs consumer SSD to see the problem with consumer hardware for ZFS. For Proxmox itself you want something like an NVME with DRAM, specifically underprovisioned for an unused space buffer for the drive controller to use for wear leveling.

ZFS is great, but to take advantage of it’s positives you need the right drives, consumer drives get eaten alive as @scrubbles@poptalk.scrubbles.tech mentioned and your IO delay will be unbearable. I use Intel enterprise SSDs and have no issues.

If it’s the same then after installing docker, creating a vaultwarden user, adding said user to docker group, and creating your vaultwarden directories, all that’s left is to curl the install script and answer the questions it asks.

I use bitwarden and the setup was fairly standard with the helper script. I use my own isolated proxy for all my services so that was already built. I haven’t used vaultwarden but if anyone that has used both can tell me the differences I could maybe help out.

TheLowestStone at lemmy dot world DarkDecay at lemmy dot world

I’ve ran jitsi for 4 years now. You can keep your personal variables in an environment file that doesn’t really change and pull down a new compose file whenever you want to update. Ever since the switch to docker from native install it has made things much easier to maintain. I’m using a lxc with debian 12. 4 cores and 4gb ram. The only reason I’ve allocated that many resources is because we use it to record a podcast with anywhere from 4 to 10 people on the server at a time. As far as bitrate, resolution, etc, that’s all handled within your env file. You’d have to look at the docs to see what’s available for you to choose from.

Before you buy anything, put some of the same content that buffers on a USB stick or powered drive and play it directly from the pi4. Also connect via ethernet to your router from another PC and check your dl speed from the NFS share.

CPU is only one factor regarding specs, a small one at that. What kind of t/s performance are you getting with a standard 13B model?

What are your laptop specs?

Ollama without a GPU is pretty useless unless you’re using with Apple silicon. I’d just get rid of it until you get a GPU.

I guess I don’t understand. You followed the docker installation directions correctly and it didn’t work or you modified the directions in a way that you prefer and it didn’t work?

I have it installed for a few years now. I started with the AIO but moved to the separate container install after AIO was deprecated. I imagine the install process is too complex for portainer. https://docs.funkwhale.audio/stable/administrator/installation/docker.html

I did steps 1-4 and skipped the rest because I already have a proxy server running. Don’t remember anything related to snapd though. Mine is running in a Debian 11 VM on proxmox instead of an LXC, but the process should be the same. Also they have a matrix channel for help https://matrix.to/#/#funkwhale-support:matrix.org

From what I remember it was relatively painless to install, but upgrading can be a chore, especially this last upgrade. My main interest in FW was the federation aspect as far as finding new music. If you don’t care about federation, maybe a simpler option would work better for you.

At the very least you need to install a webserver and you need a proxy of some kind. If you truly want old school you can just create html pages hosted from the root of your webserver (although there are now easier modern ways to do this, you might learn more the classic way rather than using a CMS).

You will want a reverse proxy to lie between your webserver and the internet that handles SSL. Let’s Encrypt is a good option to generate a cert so that you only expose port 443 on your router to the internet and your webserver. You’ll have to open port 80 to generate the cert but can close it again once generated. Then you will have https.

That’s the basics. The how-to’s are easy to find online.