So far I just hand roll my docker-compose (at home, anyway). However, docker-compose does also support overrides via yaml merging, maybe that’s worth looking into?
My idea with that is to have a base compose that configures also my services and then to have a few override yamls with environment specific stuff (like prod, local, …)
This is similar to Kustomize from kubernetes land which I’ve worked with in the past
some esoteric devices and plugins don't support them. In fact, some don't even support HTTP POST properly and will only be able to put form parameters in the URL query string (though you still need to insist on requiring a proper POST method, don't be an animal).
This gave me a chuckle. Good, practical advice for smaller APIs. Bigger orgs are likely to have distributed tracing etc but for a one man show it’s good to have input on what’s proved actually useful and necessary.
Usenet “Block Accounts” are accounts where Usenet access is purchased by the gigabyte (GB). For example, a 100 GB block account will allow you to download up to 100 GB of data from a Usenet feed. Most block accounts have no expiration date so you can use them for years. Many people use block accounts as backup accounts to fill in files missing from their main Usenet feed.
Yep, k8s is for people who need regular capacity scaling and high availability. Self hosting images is a static website, perfect for an S3 bucket or similar
Actually I’ve just taken a look and found the feature that you are talking about! I totally misunderstood, I thought you meant the comments under a post which is why I was confused. There already is a view of all comments on one pile, and those don’t seem to be threaded… which to me is madness. I don’t really see the added value of that view but I totally agree that, given that is exists, it should be threaded.
Maybe we don’t mean the same thing. Comments on Lemmy are indented and under their parent comments, just like on Reddit, and you can follow the conversation that way. That’s what I mean by threading.
But comments are already threaded… the only change here that I can see would be to throw all the comments onto one pile instead of splitting them out by post.
To be fair a lot of ORMs provide updated_at or similar, so if you have a RESTful API you could just take that, or the max of all of them if you’re doing a more complex query. It might be a bit suboptimal but it shouldn’t be too expensive.
Now you can make use of the If-Modified-Since header. Return 304-not-modified if the data hasn’t changed. Now you can intelligently utilise the the client’s caching capability without sacrificing visibility and control. Using this header will let you serve new content instantly and also cache indefinitely. The best of both worlds.
I don’t find that behaviour natural unless there is a hard conflict or I request it. So I guess it’s just a philosophical difference that led me to having a bad tint with it.
Worth noting the thing that conda does well is handle system-level dependencies, there are a lot more binaries available there (beyond just Python packages) that make it easier to install packages without having to compile C++ code or something.
Besides that I hate it haha, it makes everything else so complicated
I’ve also not had great experiences with poetry, it’s supposed to use the lock file to lock in dependencies but whenever I did anything the lock file was always being updated which kind of defeats the point. I’m sure it was user error but the fact that the lock file doesn’t stay static by default is already weird to me
So far I just hand roll my docker-compose (at home, anyway). However, docker-compose does also support overrides via yaml merging, maybe that’s worth looking into?
My idea with that is to have a base compose that configures also my services and then to have a few override yamls with environment specific stuff (like prod, local, …)
This is similar to Kustomize from kubernetes land which I’ve worked with in the past