Our baby was capable of sending these signals when she was a few weeks. So most pees she does hanging above the sink. This saves so many diapers, crazy. And much more comfortable for her to never have a wet butt, not even a minute. Would recommend!
I think within the next few months we can actually get her to go to the potty by herself. She’s 15 months now.
This industry wasn’t just good. It did destroy babies sensitivity to soiling.
I had this idea / pet project once where I did exactly this for email. Emails would immediately bounce with payment link and explanation. If you paid you get credit on a ledger per email address. Only then the mail goes through.
You can also integrate it in clients by adding payment/reward claim headers.
If Kargo requires R/W access to GitHub, and auto updates charts/images, isn’t that asking for your production environment to be infected by a change prepared and cultured in your dev environment and then auto updating / hiding itself into prod freight?
We disallow writing back to GitHub to avoid this issue, and manage stages through branches, combined with directories for overlays. Things can get out of sync, but comparing branches is easily automated.
If the image doesn’t leave the device and only the hash does… What is stopping one from uploading existing public images, banning a whole lot of innocent people?
Honestly, this seems like little. We should be wary of the source we try to pull, but given how easy it is to upload something malicious you’d expect thousands of images of this kind. Maybe DockerHub is already detecting and deleting these packages?
Or why aren’t more people interested in this?
Not sure, but maybe injecting into commonly used libraries via subdependencies is seen as a more effective method, getting more focus. Would be interesting to have a broader analysis of malicious artifacts!
I’ve been wondering about this too and always used full sha’s until now. But recently I’ve made an action myself: You actually need to publish the action to the marketplace with each tag manually. It feels like there might be more going on.
Is GitHub storing those published tags and avoiding tampering by only letting you use those tags once? Are they warning or blocking runs if you tamper? …
I’m really curious because it seems like SUCH a giant risk otherwise.
Really sounds like an awesome tool. Fits right into the serverless / JAMStack kind of systems too. Just like Netlify CMS.
I was actually in the process of tweaking Netlify CMS to be more easily hostable yourself without depending on the Netlify Pro plans as much. Basically involves hosting a combination of Netlify Identity and Git Gateway compliant backends in GCP CloudRun or AWS Lambda. Maybe even making it easy to configure a build pipeline on CloudBuild.
I wanted to use this for small business websites, but also configuration management and translations for projects at work. Sounds like FlyCode is a great (not self-built) alternative I can recommend. Great business model as well. Almost no databases needed (auth only?) and easy to host stateless on serverless offerings. Scales linearly
I think within the next few months we can actually get her to go to the potty by herself. She’s 15 months now.
This industry wasn’t just good. It did destroy babies sensitivity to soiling.