If I wasn't so lazy (and cared more) I should probably just setup my own instance. But none of the above prerequisites have been met.
@OpinionatedGeek @d3z If you do go a bit further with setting up an instance, I'm happy to have my brains picked.
(I feel confident in saying that now that zombie season has ended)
@OpinionatedGeek @d3z nitech.online is running on a DigitalOcean droplet. Over the last 14 days (when traffic picked up again) it has been using:
- <6% of 1 vCPU
- ~75% of 2GB RAM
- ~10GB of disk space
@OpinionatedGeek @d3z There's been about 10 people active in the last week, 5 people active today.
It definitely needs the 2GB of RAM, IMO. I was trying to do upgrades earlier in the year and the Docker builds were failing with RAM issues on 1GB. That's generally how I've been handling installation, and upgrades (via Docker images).
@OpinionatedGeek @d3z There are dedicated Mastodon hosting providers that might be a better compromise between home server and running a VPS like I'm doing. I tried them out about 4 years ago, but the cost ramped up very quickly for more than a couple of users, but I think it's probably more cost-effective now.
@OpinionatedGeek @d3z I've done the same with IMAP+SMTP. It really helps to gain an understanding, but it really doesn't do much in the long term.
I kinda cheated cause I'm using the Docker containers. I can't be bothered installing and maintaining all the software from source though.
@mo @d3z Oh I fully intend to cheat with containers too! I do like the way I don't have to worry about build environments and dependencies with them, and that they make (some) network+filesystem requirements explicit. k3s on a Pi has been surprisingly good too, when Docker on Pi started annoying me.
@mo @d3z Thanks for the info! I suppose I think a hosting provider is cheating - it may be the way to do it properly, but I think I'd get a better handle on it all if I put an instance together myself first. (Like email - I've run an IMAP+SMTP server in the past and learned a lot, but I don't want to do that again!)