401–410 of 420 posts
Earlier quoted context omitted.
> I can honestly say that one of the reasons people hop onto DO is due to those amazing tutorials and documentations. Seconded.
more and more my google searches lead to DO document and tutorials.
Earlier quoted context omitted.
I was in a similar position not too long ago. I had nothing but a liberal arts degree, a miserable first career and a yawning resume gap. I just stumbled into coding and I was completely addicted. After many months cobbling together a frankenstinean tangle of Kubernetes clusters, db instances and even an AI that could write bad limericks, I got a job as a backend engineer. You have to work your tail off in this job b…
> I was in a similar position not too long ago. I had nothing but a liberal arts degree, a miserable first career and a yawning resume gap. I just stumbled into coding and I was completely addicted. ... its a life changing opportunity in a field where you get to make things for a living and there's always something new to learn. Thank you thank you thank you cloud providers Programming in the 2010s and 2020s is kind…
I've also seen cases where it clearly wasn't worth it. It just depends on the project, communication and company culture. There's something to be said for walking down a hallway to actually talk to someone.
Of course the disparity north to south is less so, as meetings can be aligned better... such as with say California, Washington, Arizona and Brazil. The fact is, value is value... if you're constantly learning and experimenting, you're ahead of the curve and can deliver value where others don't.
Earlier quoted context omitted.
Thank you for this! As someone who spends okay amount of money on DO ($40, $15, $5, $5), the title of the post gave me a bit of a scare but your comment helped me calm back down. Thank you! I used to be with AWS before (still use their S3) but now I have switched from EC2 to DO droplets. Only thing I am missing with DO is the ability to set up ACL on the firewall itself so it can only be reached via cloudflare and th…
$140 user here. I need DO to stay online for its simplicity. I simply don’t understand AWS and I’m too scared to wreak a subnet while trying to add lambdas and API Gateways. I wouldn’t mind spending double if necessary. Also, clicking in Create Droplet then on a big « $10, xGB RAM » button is incredibly clear to me. Then I « ansible » it and it’s live. Please don’t add too many services to Digital Ocean ;)
I know DO is just stretching their legs on hosted solutions beyond simple storage and droplets (compute), but these are two features I'd rather not manage myself, that have some pretty big value.
Being API compatible to AWS (or even GCP/Azure) would be relatively big... that said, would just be nice additions that would round things out a lot imho. I don't think I am really wanting for anything else (since DBaaS with PostgreSQL started).
Earlier quoted context omitted.
Thanks for posting. I run browserless.io on DO, and want to keep it that way. Many have posted about about how they use DO for small projects, and I started that same way, but now it's the muscle behind a much bigger thing. Appreciate you chiming in.
Your service looks interesting. On your homepage, "Emoji's" shouldn't have an apostrophe; it should just be "Emojis". :)
Earlier quoted context omitted.
Your service looks interesting. On your homepage, "Emoji's" shouldn't have an apostrophe; it should just be "Emojis". :)
Should it even be pluralized with an s? I always thought Emoji was one of those terms that was singular and plural.
Earlier quoted context omitted.
You keep it until x days/weeks after the servers are deactivated. Where the emails are going unnoticed, the servers getting cut off usually is noticed straight away. The story here appears to be that the backups were deleted at the same time as the servers. For the relatively small cost of those who don't subsequently pay up, you get a lot of goodwill from the majority who just messed up.
When an account on DO is late with a payment, you go through three stages: hold, suspension, termination. The hold happens right away and prevents you from creating new billable resources. Then a suspension happens several weeks later, which powers off your servers. You don’t get terminated until a couple weeks after that, at which point the data is irretrievable. The time between each stage can vary depending on how…
Earlier quoted context omitted.
I don't see that it matters. Storing data isn't free. Why should they be expected to do so in the absence of payment?
You do understand what a backup is?
Is there a simple solution for this?
DO reserves say $20 (just an example) when one spins up a new droplet, and if one forgets to pay — then, DO shuts down the server. But keeps the backups, until the GB-month cost is $20.
One could choose how much money to reserve, depending on how important the data one stored on the droplet, was. If it's just for running test: $0. Customer data: Maybe $$$ instead.
There could be a default that made the data and backup last for 2 or 3 months?
And any remaining money would be refunded, if one closes one's account or sth like that.
* * *
Actually I'll look into implementing this, in my own SaaS (which, like DO, takes monthly recurring payments and stores customer data).
Earlier quoted context omitted.
6-week vacations aren't that uncommon, which is a scenario I would expect to encounter if I was DO. If that email doesn't get seen for 6 weeks it definitely shouldn't result in all backups being deleted. Beyond that, it's not unreasonable to imagine health issues or other external circumstances putting someone out of commission for 6 weeks (or even more, making it quite subjective). All in all, from the moment of non…
> 6-week vacations aren't that uncommon I would love to live on the planet you live on
5 or 6 weeks vacation per year, + about 1 or 2 more weeks in total, because of Christmas, NYE etc, is how things work in Scandinavia.
(I feel curious about how things are, where you live )
Earlier quoted context omitted.
The other folks here are giving you a hard time, so I'll just say I actually see things differently here. Things get overlooked, card expiration dates being one of them. Deleting a backup after such a short time is really poor form. Especially because these backups only exist because people need contingencies for machine and human error. Sending a threatening email 'fix your CC in 60 days or everything goes bye-bye'…
DO sends an email when they can't charge. They send a second email 21 days later, when the account gets suspended (which doesn't deleted anything), with essentially your message, except it's 14 days instead of 60. It's five weeks really poor form but eight acceptable? Seems a bit subjective.
DO reserves say $20 (just an example) when one spins up a new droplet, and if one forgets to pay — then, DO shuts down the server. But keeps the backups, until the GB-month cost is $20.
One could choose how much money to reserve, depending on how important the data one stored on the droplet, was. If it's just for running test: $0. Customer data: Maybe $$$ instead.
There could be a default that made the backups stay for 3 months?
Any remaining money could be refunded, whenever one wants.
(also "cross-posted/replied" here: https://news.ycombinator.com/item?id=22094218 )