







I always had garbage luck with MTK devices in the past with performance.
Right out of the box, all blazing fast, but just a month later they’re down to 1/3 of their original speed. It could’ve just been me, but I went through a “buy cheap devices to dick around with” phase in college and this happened with all of them (8-10 devices maybe?).
May not be an issue now, but definitely was then.


Iirc this is an inside joke by the devs.
In Japanese, it’s Hai (yes) town, which evidently was the name of the building they spent a lot of time in during development.
I can’t find any real credible source, but some mentions of it going back 4 or 5 years.
Nah outer banks is a killer spot - wife wanted to go and take maternity pictures at the beach, so we went to the OB for the first time.
Very chill place - not a lot of nightlife as the population is so low, but you also won’t get stuck with a dirty needle on the beach or stabbed on the strip so. There’s that.
Living in NC, when I was a kid, we went to Myrtle beach once a year.
Now as a father myself, hell would freeze over before I take my runt to Myrtle.
Go to the outer banks.


Quickly read through the writeup, excellent work. I’ve been meaning to do something similar to this but haven’t been able to properly commit the time to do the research required to make it all play nice.
I’ll be doing this sometime soon 👍


It’s the type of crowd that self hosting brings. We’re very much more Lemmings than Redditors by trade, so it does make sense the community here is better.
That, and fuck reddit.


A stout. Strong and sweet.


If anybody uses this in prod from a git repo, might want to place your database creds in an .env file adjacent to your compose file then gitignore the .env.
Referenced like so:
.env contents
MYSQL_ROOT_PASSWORD=MyExamplePassword
MYSQL_ROOT_USER=MyExampleUser
docker-compose.yml contents:
MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
MYSQL_ROOT_USER: ${MYSQL_ROOT_USER}
Don’t commit secrets to git!
Damn mobile formatting.


I seen a guraffe at the zoo!