destructatronLooks like setting up mastodon (specifically hometown) is going to be harder than I thought. I first have to basically nuke away my docker infrastructure of reverse proxy and lets encrypt and move that all to the actual system, then install it the normal way and not with docker-compose. or I could just get another server and stick it on that, but it's another 5 pounds a month I'm shelling out. Arg.
@destructatron I'd like to look into this. I asume I could hook nginx up to it, and then learn about Unbound to run multiple services. I just don't want to spend more money haha.
@serrebi My issue isn't the proxy server, as it manages that stuff for me. My issue is using a docker compose file to interface with a network that's already created with another docker-compose file I used to get my docker stuff set up in the first place, then have streaming and web able to be accessed normally without something port related falling over. Hometown's docker-compose already creates an internal network for database stuff which I don't need to mess with.
@destructatron For sure. I can hardly keep things together with docker, that’s why I try not to use it unless I have to.
@destructatron It’s one of those things I know I have the capacity to learn it better, so hopefully I’ll get to do that one day
@serrebi Same, I intend to get piehole running at some point too. I am considering just geting another server for Mastodon honestly. If the database gets big I have 40GB for it to use, rather than my current server which is cluttered with various web stuff and other things I host on there.