mockingjay
Docker
mockingjay | Docker | |
---|---|---|
- | 4 | |
549 | 3,177 | |
- | 0.2% | |
0.0 | 2.5 | |
almost 2 years ago | 17 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mockingjay
We haven't tracked posts mentioning mockingjay yet.
Tracking mentions began in Dec 2020.
Docker
-
Dagger: a new way to build CI/CD pipelines
I'm not touching anything Docker anymore.
Here's the scenario: you're the unfortunate soul who received the first M1 as a new employee, and nothing Docker-related works. Cue multi-arch builds; what a rotten mess. I spent more than a week figuring out the careful orchestration that any build involving `docker manifest` needs. If you aren't within the very fine line that buildx assumes, good luck pal. How long has `docker manifest` been "experimental?" It's abandonware.
Then I decided it would be smart to point out that we don't sign our images, and so I had to figure out how to combine the `docker manifest` mess with `docker trust`, another piece of abandonware. Eventually I figured out that the way to do it was with notary[1], another (poorly documented) piece of abandonware. The new shiny thing is notation[2], which does exactly the same thing, but is nowhere near complete.
At least Google clearly signals that they are killing something, Docker just lets projects go quiet.
How long before this project lands up like the rest of them? Coincidentally, we were talking about decoupling our CI from proprietary CI, seeing this was a rollercoaster of emotions.
[1]: https://github.com/notaryproject/notary
- Notary
- Notary is a project that allows anyone to have trust over arbitrary collections of data
What are some alternatives?
shell2http - Executing shell commands via HTTP server
Postman - CLI tool for batch-sending email via any SMTP server.
Seaweed File System - SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. [Moved to: https://github.com/seaweedfs/seaweedfs]
snap - The open telemetry framework
syncthing - Open Source Continuous File Synchronization
Juju - Orchestration engine that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure (Kubernetes or otherwise).
croc - Easily and securely send things from one computer to another :crocodile: :package:
confd - Manage local application configuration files using templates and data from etcd or consul
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
Stack Up - Super simple deployment tool - think of it like 'make' for a network of servers
Documize - Modern Confluence alternative designed for internal & external docs, built with Go + EmberJS