Your ports are not mapped so the host system doesn’t know about them. You only have them exposed, which is for docker communication.

Map your ports and then you’ll be able to access them by host-ip:mapped-port.

Then you can use nginx to proxy to that.

I think the distributed feature is just a bonus really.

If I had to strawman a homelabber use case, maybe you’re a very data conscious photographer or videographer and you set up another storage array at your parents house as part of your back up system. 🤷

S3 compatible means tooling compatible. Plenty of small to medium operations who aren’t tripping over themselves to throw money at the cloud. A couple guys with hardware admin and docker admin experience is ridiculously cheaper.

Writing is a rare form of communication, borderline unique to humans. Because of that, to me, it’s fundamentally unethical to have “AI” “write” anything. It’s insulting to me on a base level, particularly when used for communication.

I’m as anti “AI” as they come but there’s a master Japanese carpenter on YouTube, Shoyan, who goes through the trouble of translating his commentary to English, someone proofs it because the grammar is usually perfect, and then runs it through a comforting racially ambiguous old man voice from ElevenLabs I think. And honestly? It works really well. It’s obviously not a natural voice but it’s not fake enough to be disorienting or annoying like the early types were.

Hell yes! That was the point of my rambling though I never quite got there. I was wondering if curriculums had caught up yet, to at least look at the modern system languages. Sounds like you’re at a good program.

If Rust had been around when I was an underclassman, I would have been totally locked into the full CompSci track. Instead, I got introduced to Java and C (and calculus…) and that looked like a nightmare compared to what I had been playing with in JS/Python land, so I noped on out of there and got a Comp Sci Lite degree.

Years later, I’m just completely in love with Rust.

My actual professional advice: cut portainer out of your learning. Stick to compose as your only docker abstraction and you’ll be a wizard in no time. I have portainer running in my sea of self hosted apps and never use it. If you let some app generate compose files for you, or even just blindly use an app’s example compose file, you’ll never fully understand what’s happening and it’ll make things much more difficult to debug.

4: yes, every container will show up in portainer. 5: I don’t know 6: this is one of the reasons why I personally hate piling layers onto tools. Very often someone else’s opinion does not jive with mine.

Our GE Profile oven did the same. Of course the software is so shit, it tripped up connecting to the VLAN I set up and now it has air fry mode and no wifi.

Maybe try switching to airplane mode on your phone while trying to onboard the oven? I’m sure it’s too late for that.

I, and then every junior I’ve onboarded as well, struggled to grasp just how important the naming conventions are for everything to just work. Models and tables must be named a certain way or you’ll be scratching your head. Model policies must be named a certain way. On and on. You can override all those, of course, but it’s just another gotcha.

If you want to use PHP, and you want to be productive, there’s no other choice in my opinion. I will say, the brain behind it is quite opinionated and most of those opinions are correct. If you don’t agree with those opinions, you will probably find yourself hating it and fighting the Laravel Magic. Give in to the magic and get shit done.