4 ms·

Ah I should have included this (I'll edit the post shortly) Think the total cost was about $850, which was (almost) matched by donations. I made a mistake and

by eieio 2y ago

Ah I should have included this (I'll edit the post shortly) Think the total cost was about $850, which was (almost) matched by donations. I made a mistake and never really spun down any infrastructure after moving to go, and also could have retired the second redis Replica I spun up; think I could have cut those costs in half if I had been focused on it. But given that donations were matching costs and there was so much else going on I wasn't super focused on that. I kept the infra up for a while after I shut down the site (to prepare graphs etc) which burned a little more money, so I'm slightly in the hole at this point but not in a major way.

isoprophlex 2y ago
I wonder what that would have cost you on Hetzner, for example. I have a dedicated 20 vCPU box with 64 GB of ram and a terabyte of SSD. Bandwidth is free... and all this for 40 eur/month. This should, especially after your Go rewrite, be enough to host everything?
- eieio 2y ago
  you're right, I probably could have saved some money by using Hertzner! But I'm used to using Digital Ocean, and most of my projects haven't had these scaling problems, and I think changing my stack ahead of launching the project would have been a mistake. If I was planning to keep the site up for long I would have moved, but in this case I knew it was temporary and so toughing it out on DO seemed like a better choice.
  - isoprophlex 2y ago
    Haha yeah of course, the click a button thing is super convenient. I recently had to rebuild my box because I left a postgres instance open on 5432 with admin:admin credentials, and without default firewalls in place it got owned immediately. That would have been less painful on DO for sure.
    - eieio 2y ago
      Yeah I think this was particularly handy for Redis - click a box to upgrade my Redis instance (or add a Replica) while maintaining data with full uptime was really really nice. Painful to use managed redis when I was debugging (let me log in! let me change stuff! give me the IP!! ahhhhh!!!!) but really nice otherwise. A little painful to think about giving that up, although I coulda run a really hefty redis setup on hertzner for very little money!

by eieio 2y ago

isoprophlex 2y ago

I wonder what that would have cost you on Hetzner, for example. I have a dedicated 20 vCPU box with 64 GB of ram and a terabyte of SSD. Bandwidth is free... and all this for 40 eur/month. This should, especially after your Go rewrite, be enough to host everything?

eieio 2y ago
you're right, I probably could have saved some money by using Hertzner! But I'm used to using Digital Ocean, and most of my projects haven't had these scaling problems, and I think changing my stack ahead of launching the project would have been a mistake. If I was planning to keep the site up for long I would have moved, but in this case I knew it was temporary and so toughing it out on DO seemed like a better choice.
- isoprophlex 2y ago
  Haha yeah of course, the click a button thing is super convenient. I recently had to rebuild my box because I left a postgres instance open on 5432 with admin:admin credentials, and without default firewalls in place it got owned immediately. That would have been less painful on DO for sure.
  - eieio 2y ago
    Yeah I think this was particularly handy for Redis - click a box to upgrade my Redis instance (or add a Replica) while maintaining data with full uptime was really really nice. Painful to use managed redis when I was debugging (let me log in! let me change stuff! give me the IP!! ahhhhh!!!!) but really nice otherwise. A little painful to think about giving that up, although I coulda run a really hefty redis setup on hertzner for very little money!