oliver

15 years gone - still unbelievable that, on this April 14th, Pete Steele left this world. His legacy still lives one but it's morbid how time flies - and for everone having the chance to experience Type O Negative live, those impressions will last forever. If you haven't, you probably missed something great but the music of "The Drab Four" will last forever and lead us through many stages in life!

Still remembered, Petrus Thomas Ratajczyk “Peter Steele” (1962-2010) 🖤💚

As I am currently thinking of exchanging my current WiFi-equipment with Omada, I was searching for a way to self-host the controller in the first step. Using my Synology's Docker-capabilities paired with a running instance of Portainer here, building a stack with Omada is quite easy:

• Assuming you have the Container Manager running and the share containing your Docker-data is "docker" on "volume1" of your Synology (may me different from your setup), create a folder named "omada" here with three sub-folders: "data", "logs" and "work"
• Enter Portainer and create a new stack with your preferred name (here: "omada-controller")
• Use the docker-compose.yaml script located here
• Assure you have the proper UID and GID for your Synology-environment (see Marius' 5-seconds-way of getting those)
• Wait for the stack to fully initialize (may depend on your Internet connection) and then navigate to http://(NAS-IP):8088 and bypass the certificate error-message. You will be forwarded to https and Port 8043, enabling you to go through the initial setup

That's it - now you are ready to adopt our first Omada-stuff in your network and your new virtual controller!