tfolbrecht

Only if they'd taken contributions without authors signing over their rights.

I usually do upstream image mirroring as part of CI. Registries are built into GitLab, AWS (ECR), GitHub, etc

Thank you for your efforts.

One of my favorite quotes of all time:

"’Tis an absolute and, as it were, a divine perfection, for a man to know how loyally to enjoy his being. We seek other conditions, by reason we do not understand the use of our own; and go out of ourselves, because we know not how there to reside. ’Tis to much purpose to go upon stilts, for, when upon stilts, we must yet walk with our legs; and, when seated upon the most elevated throne in the world, we are but seated upon our breech." — Michel de Montaigne, Essays, "Of Experience"

I like the contemporary translations floating around the web "even on the highest throne in the world, we still sit on our ass"

I’m down, I think this is an awesome idea.

If this is something you’re interested in it can be reimplemented on CloudFlare workers super easily using the awssdk for s3 (R2) and with D1 as the DB.

The docker registry container supports S3 as a storage backend you could use it locally

You can also `docker image save` then write the tarball to S3, then load to use.

JuiceFS requires a backing object store like s3/minio that it “flushes” to persist data. If you want to run it distributed it uses a few other services.

I’d use object storage if I wanted simple in the replicated, jbod disk management and access control senses of simple. If I had to use file storage I’d use boring old sftp or smb on top of zfs on a NAS

The one place I've set up button triggered runbooks was gitlab ci under scheduled jobs. Made things a lot easier for less technical people.

Looks cool! I like the style.