Live data from Hacker News

Migrating from DigitalOcean to Hetzner

isayeter.com

251–260 of 454 posts

Re: Migrating from DigitalOcean to Hetzner

#251
post #66

Earlier quoted context omitted.

"ad", with a single "d". So it's a Claude ad inside a Hetzner ad inside a decent grammar ad.

Come on can you really nitpick grammar when your original message contains: "when the libraries where[sic] no longer available" Btw this type of grammar error can be found by proofreading your posts with ChatGPT powered OpenClaw assistant.

I was joking. I notoriously write bad English but don't like using LLMs for writing. It removes personality.

Re: Migrating from DigitalOcean to Hetzner

#252
post #9

I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…

Sure, and then you realize it deleted the db to "simplify the migration" lol

Obviously I agree that AI can be useful to write boilerplate, but it's in no way something you should use blindly when trying to do a migration or anything touching prod

So, to be more precise: no, "Claude Code didn't migrate it all". Claude Code helped you write boilerplate so that you could migrate

Re: Migrating from DigitalOcean to Hetzner

#253
post #101

Earlier quoted context omitted.

I have just seen with my own eyes Claude astroturfing on a gamedev subreddit from a botting account that was picked up by Google so I could see a few of their other comments. This account's operation was going on development subs complaining about how good Claude's latest model is and how awful it is being afraid of losing one's job to AI. I know your comment is tongue-in-cheek and the poster here is kinda known, but…

It's not necessarily astroturfing. There is a seismic shift under way regarding how things get done in this business, and if you don't acknowledge it, that's weird in itself.

It's absolutely not seismic. If you've used AI for a little bit, you'll realize it's good at writing boilerplate code. Any complex logic, and you better re-read and correct the code a few times until you trust it.

Of course if all you do is "host wordpress website" (like 80% of what's "webdev" do), it will work. Now the issue is that the last 20% are the hardest to cover, and current AI methods will not get there (you need some much more complex methods, like being able to integrate logic with learning-based ML, to do this)

Re: Migrating from DigitalOcean to Hetzner

#255

Earlier quoted context omitted.

Wow a Claude add embedded into a Hetzner add. How deep does this go?

I mean if it were anyone else, yeah I might agree, but I think Salvatore is being genuine here (and have seen Claude do a similarly surprising job fixing ops issues).

I don't think so. I think he's clearly abusing language (saying "Claude Code migrated the stufff", rather than "I migrated the stuff after using Claude to help write boilerplate, then I went on double-checking it, testing it, and then running it")

Re: Migrating from DigitalOcean to Hetzner

#256
post #9

I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…

Sure, and then you realize it deleted the db to "simplify the migration" lol Obviously I agree that AI can be useful to write boilerplate, but it's in no way something you should use blindly when trying to do a migration or anything touching prod So, to be more precise: no, "Claude Code didn't migrate it all". Claude Code helped you write boilerplate so that you could migrate

[deleted]

Re: Migrating from DigitalOcean to Hetzner

#257
post #21

Earlier quoted context omitted.

You can get an (a bit less than) a full employee for that. And that's a better ROI than just throwing it away.

I don't think you can get someone decent in a tech related job for that much money anywhere.

Companies have other employees than just techbros and in many cases they're more valuable.

Re: Migrating from DigitalOcean to Hetzner

#258

Earlier quoted context omitted.

> Because with a single-server setup like this, I'd imagine that hardware ... Yeah. This blog post reads like it was written by someone who didn't think things through and just focused on hyper-agressive cost-cutting. I bet their DigitalOcean vm did live migrations and supported snapshots. You can get that at Hetzner but only in their cloud product. You absolutely will not get that in Hetzner bare-metal. If your HD o…

Surely you must've noticed that pretty much all of their bare metal offerings ("dedicated" and the stuff on "auction") have multiple disks, allowing for various RAID configurations?

> Surely you must've noticed that pretty much all of their bare metal offerings ("dedicated" and the stuff on "auction") have multiple disks, allowing for various RAID configurations?

I don't know where to start with this comment. Do I really need to spell out the difference between cloud and bare metal ?

A few examples...

    - Live migration ? Cloud only.
    - Snapshots ? Cloud only.
    - Want to increase disk space ?  Tick box in cloud vs. replace disks (or move to different machine) and re-install/restore in bare metal....
    - Want to increase RAM ? Tick box in cloud vs. shutdown, pull out of rack, install new chips (or move to different machine and re-install/restore)....
    - Want to upgrade to a beefier processor ? Tick box in cloud vs move to a completely different machine and re-install/restore

Re: Migrating from DigitalOcean to Hetzner

#259
post #9

I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…

Not every fscking story has to be about AI.

They didn't make it about AI, they mentioned a tool that helped with the migration. I find it relevant and helpful to know.

I don't see it as much different from "I used script X to do it" or something.

Re: Migrating from DigitalOcean to Hetzner

#260

Earlier quoted context omitted.

Surely you must've noticed that pretty much all of their bare metal offerings ("dedicated" and the stuff on "auction") have multiple disks, allowing for various RAID configurations?

> Surely you must've noticed that pretty much all of their bare metal offerings ("dedicated" and the stuff on "auction") have multiple disks, allowing for various RAID configurations? I don't know where to start with this comment. Do I really need to spell out the difference between cloud and bare metal ? A few examples... - Live migration ? Cloud only. - Snapshots ? Cloud only. - Want to increase disk space ? Tick b…

Well you did say your data is lost when a disk fails, which is not true. Parent pointed out that for you.

Yeah you pay for and get additional stuff with cloud. Nobody disputed that.

Post reply on HN