Right. Then if this would have been a locally hosted scenario, it’s like making a post to complain about the service of their electricity company or ISP. Could similarly be reasonably considered on- or offtopic. But I think this sub is more in the spirit of “there is no cloud, just someone elses computer”. I’m with mod on this one.

Just a small number of base images (ubuntu:, alpine:, debian:) are routinely synced, and anything else is built in CI from Containerfiles. Those are backed up. So as long as backups are intact can recover from loss of the image store even without internet.

I also have a two-tier container image storage anyway which gives redundancfor the built images but thats more of a side-effect of workarounds… Anyway, the “source of truth” docker-registry which is pushed to is only exposed internally to the one who needs to do authenticated push, and to the second layer of pull-through caches which the internal servers actually pull from. So backups aside, images that are in active use already at least three copies (push-registry, pull-registry, and whoevers running it). The mirrored public images are a separate chain alltogether.

This has been running for a while so all handwired from component services. A dedicated Forgejo deployment looks like it could serve for a large part of above in one package today. Plus it conveniently syncs external git dependencies.

If not for political reasons then why limit first version to Google/GitHub rather than starting with generic OIDC (which should include those two anyway)?

We also took your feedback seriously and we are now implementing proper sign-in options like: Google GitHub (and more coming later)

Partitioning in the Debian installer being half-broken is something nobody talks about but IME still a thing.

What do is step through the installer to the point where you’re at, ctrl+F* to get a shell, set it up manually using fdisk/mdadm/lvm/cryptsetup/mkfs, and then back again to rescan and just assign the mounts and filesystems

I think I still have a half-written guide for just this in drafts somewhere actually. If you get stuck you can DM and maybe I dig something up

Both can be true.

I think such character assessment and calling names is unnecessary and off-topic here though. Better engage with substance than judging by vibes and doing ad-hominem.

Called it.

https://feddit.online/post/1372107/comment/6758185

No one listen grug til chicken come to roost

I guess they now have large enough number of users that it would be wise to shift some focus to supply-chain security from growth-hacking.

This is growing pains.

Cool! Keeping up with platform changes is a challenge for projects like this. I think to be successful beyond initial popularity you need an active community that can do this together. It’s draining for just one person - especially once you get big enough that they might actively break things just to mess with your integration. Following maintenance of alternative YouTube clients as well as searx-ng is illustrative.

Not to discourage but be prepared. Best of luck!

https://cadence.moe/blog/2022-09-01-discontinuing-bibliogram

More concretely…? What cursed endpoints is this too simple for?

https://docs.haproxy.org/3.2/configuration.html#http-request

https://docs.haproxy.org/3.2/configuration.html#7

https://docs.haproxy.org/3.2/configuration.html#11

What is an example of a “Better feature” relevant here?

HAProxy if you’re just doing containers

What makes you say that? From my experience、HAProxy a very competent, flexible, performant and scalable general proxy. It was already established when Docker came on the scene. The more container-oriented would be Traefik (or Envoy).

You are not helping!

(But also not wrong)

It’s more like busking on the street and then feeling offended about not getting any money despite people liking your music. Maybe you’re even inadvertently part of some commercial ad shoot profiting of the city vibes. Or offering free trials of a service and then being upset when nobody converts.

I don’t think things you do become “charity” just because others benefit from it and you don’t get compensated. The bar is higher than that.

No reason to expect that everyone will be in a position to do that indefinitely, especially when it comes to massive projects that turn into full time jobs.

For sure. No strings attached goes both ways.

There is one part in the post mentioning how to “pad holes” in failing areas. Maybe I should expand it with some details around aligning reserved address space.

Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.