bjorney

You can just point your domain at your local IP, e.g. 192.168.0.100

Not with 64gb ram and 16+ cores on that budget

You could set it up in docker whilst still on windows, and then all you need to do is copy/paste your compose file onto your new Linux machine, that way you aren’t struggling to learn two things at the same time (alleviates the “I don’t know if the problem is with my docker config or my host OS”)

“how dare they use the right tool for the job without taking the time to learn how to do it sub optimally first”

In my experience about ~8% better but 4x slower to transcode

scientific research papers

When JSTOR comes knocking you are going to wish it was the MPAA instead

To elaborate a bit more, there is the MySQL resource usage and the docker overhead. If you run two containers that are the same, the docker overhead will only ding you once, but the actual MySQL process will consume its own CPU and memory inside each container.

So by running two containers you are going to be using an extra couple hundred MB of RAM (whatever MySQL’s minimum memory footprint is)

it won’t necessarily take twice the resources of a single mysql container

It will as far as runtime resources

You can (and should) just use the one MySQL container for all your applications. Set up a different database/schema for each container

You can claim the free games from the website last time I checked. you don’t even need to open the games store app