usrme

Thanks for creating this, this is really fun to play around with! Is the code for this out in the open if someone would want to peek under the hood?

Same question here!

I'm right in the target audience for this as I'm about to embark on a Kubernetes certificate. What is the proportion of official K8S documentation and your own notes and how could someone differentiate between them on that site?

This is described here (https://docs.brew.sh/Tap-Trust) if you scroll down a bit.

I'd love to get a link to that comment/post!

This is actually addressed at the bottom of the page, somewhat: https://mrshu.github.io/github-statuses/#about

Agreed. If that would be too cumbersome to add, then a simple counter showing how many times a book has been recommended would help guide, me at least, a little better than just categories.

This sounds interesting. Would you be able to share more information about this style of running? I'm having a hard time imagining how this plays out in real life.

An incredible undertaking! How much testing have you done with regards to harvesting a manual configuration into Ansible, creating a new machine and then applying that to see whether the machine is a functional representation of the old machine?

The reason I'm asking is because I'm interested in how much confidence could be lent to this tool with regards to more old and obscure machines that have been running for years.

Like my guy 'diarrhea' already echoed: using CUE absolutely does not make sense at a small scale; just write your YAML and get on with your day. We were using it to generate dozens upon dozens of GitHub Actions workflows from what was essentially a single source of truth, and because CUE can export to JSON too then that single source of truth could then easily be leveraged to provide other input files to be used elsewhere.

When I got started it was much more difficult as you had to do a lot of manual work to get things started, and you really had to believe the promises that CUE offered (which I did...), but nowadays they've made so many steps in the right direction that getting something going is far quicker!

Here are a few links to whet your appetite:

- https://cue.dev/docs/getting-started-with-github-actions-cue...

- https://cue.dev/docs/drying-up-github-actions-workflows/

- https://cue.dev/docs/spotting-errors-earlier-github-actions-...

Definitely read through the CUE documentation (https://cuelang.org/docs/), watch their YouTube videos (https://www.youtube.com/@cuelang/videos), and join the community Slack channel (https://cuelang.org/community/). I've gotten a lot of help in the Slack from both enthusiastic community members and from the developers themselves whenever I've gotten stuck.

Dagger was something I looked into two or so years ago before they got consumed by the LLM and AI agent hype, and while the promise of being able to run the exact CI workflows locally seemed excellent, it seemed that there's basically no way be a Dagger user without buying into their Dagger Cloud product.

I ended up opting for CUE and GitHub Actions, and I'm glad I did as it made everything much, much simpler.

I wasn't able to see some example images or a demo video. That would be great to have before setting things up.

I've been wanting to create a similar holiday optimizer tool myself, but what you've done is marvelous! Do you take requests for new countries? I see that you're using https://date.nager.at/ as the source and country is listed, so perhaps it's easily doable?

Seconded. I've had huge success with generating workflows with CUE. Would definitely recommend it to anyone struggling with YAML.

There was actually a really terrible brown-out by Poetry (a Python dependency management and packaging tool) where they introduced sporadic failures to people's CI/CD systems: https://github.com/python-poetry/poetry/pull/6297

Thanks for mentioning these! Do you know what are the official channels they're doing the announcements in? In the post they just mention the word "usual" with no clarification.

This is covered in the official GitHub issue: https://github.com/bitnami/charts/issues/35164

Q: What will happen to the existing OCI Helm charts? A: The already packaged Helm charts will remain available at docker.io/bitnamicharts as OCI artifacts, but they will no longer receive updates. Deploying these charts will not work out-of-the-box unless you override the bundled images with valid ones. *except for the BSI images included in the free community-tier subset.

I would be really interested to see what your prompt was!

If you enjoyed this, then definitely read through Tailscale's lengthy write-up about NAT traversal: https://tailscale.com/blog/how-nat-traversal-works

I would definitely recommend adding example images directly to the main page, along with the link to the example trip. Otherwise there's nothing really to draw users in to using if they have to go searching for how the experience looks like.

Fellow aphantasiac here: it's not so much a memory of that very situation happening, for me at least, but the feeling of it happening and some of context around it.

Same goes for tragic and happy events: I can't remember their details, but I remember my emotions.

As someone with aphantasia and SDAM, this is what I've literally done for the past 4-5 years. I've kept a log of every single work day so that I could refer back to what I've done over whatever period as otherwise there is literally no chance I'd be able to recollect much of anything.

The link to the discussed talk is at the very bottom of the post: https://www.youtube.com/watch?v=ydVmzg_SJLw

The link to examples also leads to nowhere: https://cisco-open.github.io/forge/examples.

I recently came across Remote Yeah[1], but I can't vouch for its viability personally. It might help discover some companies who are at least willing to go down the remote route.

---

[1] https://remoteyeah.com/

To get around the horror that is YAML, I wholeheartedly recommend writing GitHub workflows in CUE and generating the required YAML out of them. I'm hopefully never going back to writing YAML myself!

I had no idea Vim had a terminal mode with ':ter|:terminal'! Definitely something I'll look into to improve my own Vim + Git workflow. I've usually just moved Vim to the background with Ctrl+Z, done my committing, and then moved Vim back to the foreground with 'fg'.

This is a fantastic mention! I've been commenting out my commit message lines and then saving as a way to trigger this. Feeling like a caveman...

Love the way you made that Nebraska reference!