Self Hosting

Trying to self-host is a lot of work. I’m not a techie—just a wannabe techie with some computer skills. Mainly, I have enough knowledge to recognize patterns and handle simple tasks.
With the advent of ChatGPT (which I’ve found to be the best so far), I’m trying to step out of my comfort zone and learn new things. However, I’ve had to rely on ChatGPT for Portainer YAML files, Docker, Docker Compose, and setting up my Raspberry Pi 5 in a Pironman 5 case. I assembled the hardware myself, but when it came to the software, I needed ChatGPT’s help.
Out of the eight containers/stacks I’ve attempted to set up, only about two successfully deployed with ChatGPT’s initial guidance. The rest required a lot of tinkering—feeding logs to ChatGPT, troubleshooting errors, and making adjustments—before I finally got them working.
Why is this such a chore? I know Linux is different from Windows, but one thing I can say about Windows is that as long as software is designed for it, you just click the installer, and nine times out of ten, it works. And if it doesn’t, an update usually fixes it.
I like GUIs. The last time I dealt with the command line on a daily basis was in the DOS era. I understand that the command line can be powerful, but it’s also error-prone—one small typo can break everything. Point-and-click was a marvelous invention! #SelfHosting #TechLearning #Docker #RaspberryPi