Idk, most of the bigger VPS services don’t have anything like that. Yeah, they have higher tiers, but you usually get similar or better value as you go up.

It’s a browser for Android based on Firefox with some privacy-related settings enabled.

And it’s a school of thought I happen to agree with. :) But OP specifically called out homelab vs VPS.

I use a VPS and generate static sites using Hugo. Works fine.

I could host it in my network, but I don’t see a point, and I’d really rather not have a power outage or loss of internet break my site (much more likely at home than at a datacenter). I host pretty much everything else within my network though.

What’s with that crazy price jump from $23/year to $18/month? Doubling RAM and cores increases prices by 9x? 2GB RAM and 2 cores is $5-6 at Hetzner, no idea how they think $18/month for 1GB RAM and 2 cores is competitive in any way, that’s a bit of a dark pattern IMO…

I switched from Vultr to Hetzner, mostly because I was annoyed at the screen-blocking prompt to accept the new EULA (included forced arbitration). Hetzner still has the forced arbitration, but the prices are good and I haven’t found anything to be especially annoyed at.

Oh cool, I’ll definitely look into that.

And honestly, the one I need more is a test group for CI, for things like coverage reporting and whatnot. If I can get that and if having multiple package indexes works properly (i.e. it can check my private repo first, and then pypi), I can probably port our projects to uv, at which point it’s an internal discussion instead of a technical one.

Good call. We have some other tech debt related to our docker usage, so I’ll add this to the list.

I’m not really worried about the migration work, from what I can tell it’s basically just moving a few things around. I’m more worried about losing features the team likes largely for performance reasons.

Our primary use cases are:

• dev tools - standardize versions of tools like black, pylint, etc; not necessary if we move to ruff, we’ll just standardize on a version of that (like we do with poetry today)
• tests - extra deps for CI/CD for things like coverage reports

I like the syntax poetry has, but I’d be willing to use something else, like in PEP 735.

One thing we also need is a way to define additional package repos since we use an internal repo. I didn’t see that called out in the PEP, and I haven’t looked at uv enough to know what their plan is, but this issue seems to be intended to fix it. We specify a specific repo for a handful of packages in each project, and we need that to work as well.

I’m currently looking to use ruff to replace some of our dev tools, and I’ll look back at uv in another release or two to see what the progress is on our blockers.

Yeah, it certainly looks nice, but my problems are:

• everything runs in a docker container locally, so I don’t think the caching is going to be a huge win
• we have a half-dozen teams and a dozen repositories or so, across three time zones, so big changes require a fair amount of effort
• we just got through porting to poetry to split into dependency groups, and going back to not having that is a tough sell

So for me, it needs to at least have feature parity w/ poetry to seriously consider.

Looks like it has basic support:

• required-python = "..."
• dependencies = [ ... ]

Once it gets dependency groups, I’ll try it out. I’m currently using poetry, which works, but I’m always interested in better perf.

We’re using poetry and it solves our problems. I’ll have to look into uv, but I don’t feel in any rush to switch away from poetry.

Really? That’s so odd, I thought as long as you’re not running an exit node, you should be fine. TIL, I’ll have to check my ISP’s policies before setting one up then.

Yeah, 100M is a no-go for me since my ISP provides much more than 100M, and streaming full-res videos would bottleneck that pretty quick.

1G is probably fine for us, but we’ll probably go 2.5G minimum the next time I need to swap out switches, maybe 10G.

Yeah, I trust Mikrotik much more than Trendnet, though I’m happy to use Trendnet for internal switches.

the manufacture published a firmware patch for before any public disclosure was made

They were pretty quick for the stable branch, so I guess the miss is prioritizing it for LTS. But if it’s just the one time, I’m completely fine with that.

Do be aware that Backblaze drive access patterns will probably be quite different from yours. So if there’s a really good deal on something with a bit higher failure rate, but your usage pattern is pretty tame, it may be worth taking the gamble.

But at least you mean well.

I don’t think you even need to try very hard…

One that I wasn’t sure about asked about a NAS. It seemed the question was about dedicated NAS devices, and I built my own NAS (desktop PC + drives + btrfs + samba, etc).

I answered “no,” but I think it would be interesting to capture that distinction in the next one. I.e. Do you use a NAS product?

• Yes (commercial)
• Yes (DIY)
• No

And then a follow-up about what that NAS offers (i.e. just NAS stuff, or can it host apps?).