Tootfinder

Edit: question answered successfully! Ty!
OK folks, I need some #docker advice for those gurus out there. A boost would be appreciated to get it in front of knowledgeable eyes.
I have a container running postgresql for mastodon. I would like to tweak the conf file for postgresql now that I have things going.
What is the safest way to do this on a running container?
Can I stop the instance with docker stop and then restart it and it will simply see the new postgresql.conf specified in the original docker run command?
I'm getting more comfortable with docker.. but not *that* comfortable, so I'm still worried that if I restart it'll break somehow lol.
I want to make sure I do this right so I don't wreck what appears to be a running and reasonably happy container :)
I'm running docker in a colima virtual machine on macOS.
#mastoAdmin #docker #colima #postgresql

still 🆙
#selfhost #mastoadmin #colima #docker

ok, really for sure this time.
i think it's going to be stable.
I think.
#mastoAdmin #selfhost #newOldimac #colima #docker

making a script to backup the postgresql and redis docker containers... so I can have this run everyday to ensure I don't lose anything if/when docker collapses.
I also noticed that the docker containers all use UTC time, which is annoying, and who knows maybe that has something to do with the instability? so i synced it to America/Vancouver
Also... I know "America" is the continent, not the country in this context. But there is more than one Vancouver on the American continent. Canada/Vancouver would be better, no?
#random #selfhost #mastoadmin #docker #colima

It's a day later and #footiMac and #newOldiMac are still up and running. Disk usage is stable. Current RAM usage for the database has gone up to 3GB from 1GB since 9PM last night. I'd like to know why. It's not any busier.
I'm running the backup script then later today I'll see if I can investigate more on why the RAM usage fluctuates so much.
I would like to know why it is more stable. Is it because I've simply given it enough room to expand and contract in the colima VM?
Is it because I set the clocks to the same timezone?
Inquiring minds... but I am happy that it is happy. And I have learned a lot and gotten more comfortable with docker. Which has been a goal almost since I joined Mastodon in Nov 2022.
I’m hoping to look for a new macMini now to replace #newOldiMac. If I can get that an SSD to replace the failing SSD in #footiMac and a large HDD for backup that'd be great.
#docker #mastoAdmin #colima #iMac

this is the longest that my #selfhost instance has been online in 5 days lol. Starting to feel confident. Probably jinxing it…
#mastoadmin #colima #macos #docker #jinx

ok. docker backup script is solid.
it will:
1) mastodon db dumped in container and copied outside
2) redis file saved in and outside
3) both containers snapshotted and saved outside.
#selfhost #mastoadmin #colima #macos #docker #jinx

success.
docker restart does not jeopardize anything as long as a volume is specified at runtime to preserve the data.
successfully restarted with new conf file and we're now green across the board and hopefully tuned for the slightly larger resources available from #newOldiMac
#docker #mastoAdmin #docker #colima #postgresql #selfhost

I think it is funny, ironic, nerdy, and meta (the proper literal sense) that I have maxed out the 2017 iMac by wanting to install btop while watching it be maxed out on htop.
And yet... it's still posting this, so if stuff doesn't break down now, surely it never will? Even the swap is having a moment. Ooof. I need to be nicer to my machines. lol
#newOldimac #selfhost #mastoAdmin #footiMac #docker #colima #homebrew

just tweaked/upped web concurrrency and max threads settings in my .env.production settings for Mastodon to give #footiMac a few more processes to handle requests and things are humming along nicely.
I think a big takeway for me on this #selfhost journey is that except on the very smallest one person and minimal followers instance, the database (and possibly redis) function should always be on a different machine or container from mastodon.
#footiMac was clearly having real trouble handling the database activity once it got busy. Even with an SSD now with two bad blocks (which may have been caused by that over-activity), it is way more stable.
#newOldiMac #docker #mastoAdmin #colima #iMac