taizou @lion@computerfairi.es

alright I've switched http://notes.12bit.club over now, I solved like 3 problems it was having but it is much more complex than the others so again if anyone wants to dick around with it and see if they can find anything broken i'd appreciate

and with that I Think all my public facing websites that use PHP are running it through Docker now..!! Still a few other things remaining like my Twitter bots.... which I'd also like to get working on non-twitter sites sometime...

(reposted bc wrong link)

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

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

so...i got docker installed on the server... got my container up and running... web server pointed at it... all that worked fine

the new and cool problem i now face is that it's unable to connect to the mysql server on the host, despite this working fine for me locally. it doesn't even fail in a useful way either, it just times out. if i ping the hostname that's supposed to map to the host's internal network, it responds fine. but doesn't respond for mysql

going to fucking bed again

Realised why that was happening, the table dump actually had TABLESPACE `innodb_system` in it, which caused the reimported table to always go in the massive ibdata file. Have converted everything to file per table properly now. But that was still kind of a futile exercise considering theres still no way to shrink ibdata without dumping, deleting and recreating all the databases. And I'm just not gonna do that until I fucking need to because I have plenty of space for docker atm