Linode is top tier. Support is great. Interface makes sense. Instances are fast. One of the things that led me to DO was the $5/mo instances though. It's hard to resist a cheap personal server you can host all your legacy projects stuff on.
Linode is top tier. Support is great. Interface makes sense. Instances are fast. One of the things that led me to DO was the $5/mo instances though. It's hard to resist a cheap personal server you can host all your legacy projects stuff on.
I don't have a lot of prod code in golang. It's just a gogs server, the rest of is in other languages. All of which the best practice is pulling down requirements (some of which build c-extensions against headers which versions differ) on the server.
As a side note gogs has been really great. For those who don't know you can grab it at https://gogs.io/.
Should be mentioned though that it hasn't always been this way. Before they rebuilt their management infrastructure they were hacked a couple of times and their response was... Not great: https://news.ycombinator.com/item?id=5552756
They've made a lot of progress since then but they were also DDoSed quite heavily recently which brought a lot of downtime.
It was also a pleasant surprise seeing a Brad Fitzpatrick testimonial on their homepage https://www.scaleway.com/
I've seen this issue twice myself, so I'd say it's probably more common than we'd want it to be.
Alternatively you could just add a swap file.