photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

244
active users

#proxmox

13 posts12 participants0 posts today
Thib<p>Continuing on my homelab summer series: I overengineered my homelab because I don't want to pay cloud providers.</p><p>I could just install k3s on my server, but I'm installing a hypervisor instead. Not only does it give me more stability and flexibility, it also lets me experiment without putting my production at risk.</p><p>Also, I don't want to end up with a massive cloud bill.</p><p><a href="https://ergaster.org/posts/2025/08/04-overegineering-homelab/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ergaster.org/posts/2025/08/04-</span><span class="invisible">overegineering-homelab/</span></a></p><p><a href="https://mamot.fr/tags/selfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfHosting</span></a> <a href="https://mamot.fr/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a> <a href="https://mamot.fr/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxmox</span></a></p>

Just when I thought I had my #Proxmox #Frigate #HomeAssistant setup working to push snapshots up to a remote server on a several minute interval, all of the images would disappear for a while.

I could not figure out what was going on until I recalled that I have a separate remote machine also rsyncing to this server. The other machine was deleting the files my local machine was sending up but not deleting the directories.

I've moved where I'm pushing files to a different folder on the server

I have something else to be thankful for today. At this moment in time I am busy restoring functionality on systems so that I will be able to resume important remote tasks, which shall enable me to restore the level that I am used to, when it comes down to actual value of goods

This work is highly specialized and needs a set of computing systems, communication systems which use GSM messaging systems and other means of signalling, in order to properly Act, monitor react and deploy the remote systems, of which a set of those are managed deployed monitored and configured through Proxmox.

@gyptazy has made incredibly wonderful contributions to the community of Open Source and I'm specifically highlighting his work in for example the great Proxmox load balancer.

Through the Work Of Him and other hundreds to thousands nameless Open Source coders, programmers en hackers am I able to do this work.

I am fortunate enough to have virtually met him here on the FediVerse through a beautiful forward that @stefano has made.

Without the work of this incredible people none of this would have been possible. I would be sitting watching this beautiful scenery that I would have made myself with props

There would not be any Open Source Operating System driving the displays.

Being Grateful is important. Giving Thanks sends a beautifully modulated Pulse of Energy through the Universe to everyone.

I am thankful to you all

Da mir heute wetterbedingt etwas fad ist, habe ich daheim auf die Schnelle mal #Technitium #DNS in einem #Proxmox #LXC installiert. Habe hier in den letzten Tagen den einen oder anderen Beitrag dazu gelesen und ihr kennt mich ja, ich bin halt ein Spielkind. :wink:

Somit habe ich aktuell als Haupt DNS #AdguardHome mit lokalen #Unbound (#OPNSense) und zum Testen einen #PiHole und jetzt eben auch Technitium ebenfalls mit lokalen Unbound.

Bin gespannt, ob eines der beiden Adguard Home ablösen wird. Vorteil von Technitium ist schon mal, dass der lokale Unbound ohne rumbasteln verwendet werden kann, da dies in den Boardmitteln bereits enthalten ist.

AHA!!! I believe I have cracked the #Frigate #HomeAssistant #Proxmox nut! I can now get a snapshot from a camera via Frigate to Home Assistant in the correct resolution and then upload that via SSH and RSYNC to a remote server!

The trick was setting up the camera as a second camera with only a detection stream using the full resolution but then turning off detection and adding height and width parameters. Next toot will be the code.

For #Proxmox and/or #ProxLB I would wish a function for upgrading a cluster.

That is: download new packages/kernel, install them on node A, rebalance VMs/containers, reboot noide A when ready, after reboot rebalance everything again, wait for Ceph to be healthy, proceed with node B, and so on...

But maybe it's just me...

:boost_ok:

For a #homelab/#selfhosted project, would there be any reason to pick one of #freebsd or #openbsd ? (Just because #netbsd seems amazingly portable it also interests me).
So far I mostly run #Linux containers with #podman and VMs with #proxmox, the only *BSD VM running is #opnsense. And so far #btrfs seems pretty good alternative to #zfs.
I hear the network stack is supposed to be better and the system overall more “unified” but I fail to see what to try or do with it.

I've finally completed most of the guides I was planning on adding to my #Homelab Wiki - now it's got guides on setting up #Portainer, #Immich, #Jellyfin, #ErsatzTV, #OpenMediaVault (#OMV), and even #HomeAssistant - all of these (besides Jellyfin and ErsatzTV, those are on #Proxmox) are hosted on my #RaspberryPi in my homelab.

Most importantly though, I've organised the wiki a lil better - into different
courses. The first course details the type of hardware you're going to want to assemble - a beefy server (with only consumer parts) or a mini server (i.e. an #SBC), or whether you'd like to deploy a #NAS, followed by a course to setting up and managing a hypervisor (including #ESXi, but really, use Proxmox - which is #FOSS and plain better).

There's also a whole course on all sorts of 'host deployment environments' (i.e. where your application is hosted on, like
#VM, #Docker, #Kubernetes, and #LXC) you could have in your homelab. (One of the) Most importantly, a course on networking - which covers valuable topics like setting up a domain, free or paid, and setting up a reverse proxy for serving your hosted applications publicly, securely.

There's still some stuffs I gotta add, like a complete guide on setting up
#TrueNAS (which I've set up for many years at this point, without much documentation on how I did it - so I gotta find an opp to replicate it, when I have extra hardware maybe), but I'm pretty happy with it at this point. If you're planning to get into homelabbing, or even if you're already in it - maybe check it out ​:blobfoxcat:

🔗 https://github.com/irfanhakim-as/homelab-wiki

RE: https://sakurajima.social/notes/a9so79m6ze

My #homelab wiki is getting really complicated to organise and write for haha, but it's definitely getting more interesting topics like more #RaspberryPi stuffs, #Docker, and some cool stuffs like #OpenMediaVault and #HomeAssistant. I'm taking my sweet time to update them 'properly' and hope it'll all link/piece together sensibly in the end.

This is partially thanks to me embracing the fact that I just don't (yet) have the resources for a
standalone 'mega' homelab (#Proxmox & #Kubernetes based) server cluster that I could simply throw everything to it, hence supplementing that setup with tinier SBC-based servers. Gives me a bit of peace of mind too that things are now more 'spread out'.

The most interesting bit will probably be when I manage to explore replicating a mini version of my
#RKE2 Kubernetes cluster, on a single (or at most, two) Raspberry Pi node - maybe based on #k3s, assuming that's better. I'm just not there yet cos I'm kinda reluctant if using something like #k8s on RPi makes much sense since I'm expecting a lot of resources will be wasted that way, when hosting on Docker alone (i.e. on #Portainer) should be leaner.

🔗 Anyway, if y'all wanna keep an eye on it: https://github.com/irfanhakim-as/homelab-wiki

Wiki about everything Homelab. Contribute to irfanhakim-as/homelab-wiki development by creating an account on GitHub.
GitHubGitHub - irfanhakim-as/homelab-wiki: Wiki about everything HomelabWiki about everything Homelab. Contribute to irfanhakim-as/homelab-wiki development by creating an account on GitHub.

I'm still trying to figure out the best approach to capture snapshots at regular intervals using #Frigate and possibly #HomeAssistant from the high resolution stream of a bunch of IP cams. Then down-scale them to a smaller resolution. Then RSYNC them to a remote server. And only retain the last ~100 images per IP cam on the remote server (and do cleanup locally).

Of course I cannot use RSYNC or Image Magick on Frigate because of the way it's installed (in a container in #ProxMox

🤔

Adventures in #Debian #Linux running inside a #ProxMox VM... Managed to get remote desktop working which makes it easier to do things in the GUI versus the ProxMox default setup. But now trying to setup an ftp server isn't working. I've got something misconfigured so I'm unable to login to it via ftp/SFTP/ssh successfully.

For my specific use case I have to use port 21 and old school FTP protocol. This machine is behind a firewall and I'll block remote access.

#ProxMox tip: if your #VM contains a large chunk of data that doesn't need to be backed up via the built-in mechanism, segregate that out to a separate virtual drive, uncheck "Backup", and softlink that drive's mount point to whatever folder expects the data. 👍