Whoop whoop! The newest addition to the server rack is installed and running great!
After noticing so many beautiful #RaspberryPi 4's of mine laying around, I figured I'd put them to some good use as a #cluster and running a self-hosted #webserver , instead of paying money for a service to do it every month...
@adingbatponder I currently have two different web apps running on a cluster of #RaspberryPi 4's that use a fantastic debian-based OS called #DietPi...I use a Compose file with Docker Swarm to run multiple instances of the containers on all the nodes, and manage it via #portainer.
Pretty straightforward to get all the nodes set up and runs great! You can do the same from NixOS by adding
... but I did it through ssh'ing into my home server, and navigated around with cd .. across multiple folders. Even figured out how to search for a folder.
Ahhh...nothing better than the sound of snapping in the heatsink and case of a fresh, new #RaspberryPi 5!!! Still haven't completely settled on the application stack to run on this bad boy, but I've got a nice little starting point in mind...
Just 2 more stacks to move from my old #Portainer server to my new one!
I originally set the new one up as an agent connected to the old one thinking there would be a way to change an agent into a standalone server but there isn't
So the 5 stacks I'd re-created on the agent (and moved their data etc) had to be re-done!
Was it my own fault for not just setting it up as a server to start with? Yes. Absolutely.
Has there been downtime? Yes. Some.
Do I care because it's self-hosted / homelab things? Not really. I can work around them and anything critical (looking at you DNS-based-ad-blocking) I already had a second instance running because I made that mistake before! :P
The reason I don’t personally run #proxmox in my #homelab is the host machine needing a static local IP address that must also be hardcoded in the hosts file (see https://www.servethehome.com/how-to-change-primary-proxmox-ve-ip-address/). I understand why it is necessary for the networking virtualization but I personally don't like it for a dynamic environment like the homelab.
Docker with #Portainer seems to be a more flexible solution with obviously a different feature set.
The home lab now has some pretty dashboards thanks to Grafana. This was my most difficult setup so far, and my first docker stack with more than one app installed in it.
Ran into issues with the stack crashing a LOT in portainer while I fiddled with it. :yikes: Not sure I made the right choice as to the appropriate server to install it.
Weiter geht es mit #Docker for Tuxi. Ich habe in #Portainer eine Volume erstellt, das per #CIFS eine Freigabe meines NAS einbindet.
Diese Freigabe wird im Container auch eingebunden. Das Problem ist, dass ich absolut nichts in diese Freigabe schreiben kann. Selbst ein chmod 777 im Container bringt nichts.
Ich suche mir echt den Wolf, finde aber absolut nichts, was zu einer Lösung führen könnte.
Was muss ich machen, dass ich im Container in das CIFS-Volume schreiben kann? #Frage#FragDieFediverse#FragDasFediverse#Followerpower@askfedi_de
Ich spiele gerade wieder mit #Docker und möchte #Friendica damit testen. Momentan stecke ich aber bei dem Installations-Assistenten fest, und zwar bei den Angaben der Datenbank.
Beim Erstellen in #Portainer habe ich dafür folgende Environment Variablen für die Datenbank angegeben:
Wenn ich allerdings bei dem Installations-Assistenten diese Werte eingebe, werden sie nicht akzeptiert. Sollten sie aber doch. Oder habe ich irgendwo einen Denkfehler? @helpers@admins
I just had to steal this #meme from #reddit, it's about #selfhosting all your stuff. Instead of being relient on the constant threath of loosing your #google account. Or what about losing your centrally accessed #twitter account because #elonmusk thinks you are not worty of his platform?