taizou @lion@computerfairi.es

They seem fine I'm eating them

I bought them like two weeks ago and just noticed smh my head

Chat do you think an unopened box of oreos thats 3 months out of date would still be OK

2 more subsites switched over https://repo.12bit.club/ and ye olde http://fuji.12bit.club

the only one remaining (I think) that hasn't been switched is http://notes.12bit.club which didn't work with the config I used for the others & I'm not surprised tbh cos it runs mediawiki which is the most complex software running on any of them by far

I put https://hhug.me/ on it too

restarted the container today & it came up on a different subnet so all my mysql config stopped working lollll
apparently you can configure it to use a specific subnet in docker compose, so, I did that, and now it works again

i've switched over the public version of that site to use it now, so if you want to poke around https://blog.12bit.club/ and see if anything looks broken then feel free

Oh come on

and this is a version of my blog now running through php-fpm in docker!! it seems to work perfectly, loads just as fast as the old version

i'm not switching over to this for the public ver yet in case i find some problems but this is very very promising

for once i can go to bed on a high note instead of an "ugh fuck this" note

so I got the bastard working!!!!!!!!
I think my main misconception was that the docker internal host thing was like, magically mapping things to appear to connect from localhost on the host so I wouldn't have to do anything special to allow them to connect
but that's not the case, the container connects from its own IP address so I had to allow that through the firewall & allow mysql users to connect from it

@Ninji Yeah I did indeed have to do that
and it works!!!!!!! thanks for your help

@Ninji that did work yeah - but I also realised i need to actually let the container connect through the firewall & I'm getting somewhere now ​

like i'm now at the point of getting normal mysql access denied errors, i can work with this

@Ninji no, how do I find that out

@Ninji nah i'm not running mysql through docker at all, it's just an existing setup on the host machine, i'm trying to connect to that from inside the container

I still can't resolve this mysql issue though. So like for background I have extra_hosts: - "host.docker.internal:host-gateway"
configured in my docker-compose file & that's supposed to map the host machine's internal network to the hostname docker.internal.host inside the container
And that works, for some things, e.g. I can ping it, I can connect to its web server port. But not for mysql! It just times out! I don't know how to debug this!!!!

This seems bad??!?!? I very nearly misconfigured my container in a way that would have accidentally left a port exposed, but I thought "oh well it wouldn't have been _too_ bad cos the firewall would block it anyway", but apparently, no, docker just says Fuck your firewall