Obviously had to get on the #clawdbot train, but failed at step 0: run the docker-setup.sh (tries to load some dependencies that would be unneeded but also unavailable at image build).
I kind of feel that just running the install script on my main hosting machine (outside docker) is not smart, so left to do: setup separate VM in public cloud to try this out?
is it just me, or everyone else is just running the installer on their main machines? :) #selfhosting
@robin While I do have a spare m4 mac mini pro, I'm still not sure that I would run it directly, and considering the number of Docker capable hosts that I have, I was also looking the .sh script just now, as well as the compose yaml.
Maybe I will try the yaml and run those two containers outside the sh script and see how that goes.
@blackvoid Feels like pretty basic stuff that's going wrong, like it's missing the fact it's building the container (so some dependencies won't be there), while that's not a real problem. Started editing .dockerignore (also required) and looking at the other files, but I guess I wait for now.
There's also the install-cli version, but that would still run as a user on the system, doesn't feel warm and cozy really. :)
@robin Considering what it can do, and the permissions it needs, this is a true definition of security vs convenience
