• 5 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle











  • Now that I’ve finished the first draft of an article on setting up rootless Podman on Guix System, I’m using and building out a set of tools to support a new article covering an all Red Hat stack from inner loop to CI.

    So far, it’s

    • OpenShift for the platform services run on
    • Podman for my local container engine
    • Podman Compose for inner loop development
    • OpenShift Pipelines for CI
    • Shipwright for building container images locally with Buildah
    • Quay for image scanning and storage
    • OpenShift Serverless for scale-to-zero deployments


  • Some folks may not know this but Logseq has a built-in whiteboard feature too that’s also FOSS. I use it all the time to mind-map new blogposts and newsletters.

    In Logseq the starting page is always the journal page for the day. This allows you to build up content without worrying about where it should go. Once you have something you feel you can run with, then you can move it to its own page.

    EDIT: more features enabled by Logseq’s block-based (bullets) architecture over on Mastodon.




  • Logseq is FOSS and easily one of the best notetaking apps out there. It’s got whiteboards, interlinking at the block level, a big ecosystem of extensions and multiple panes so you can derive context as you write.

    It’s my choice for the majority of writing I do in my day to day and hasn’t let me down once. My only wish list feature is multiplayer but that’s coming soon.


  • Because it uses OCI images, it auto-updates like a Chromebook, and you can switch between modes, like say a gaming mode that’s a full SteamOS replacement, to a mode that gives you an entire development environment without needing to install and configure these layers or stacks of capabilities yourself.

    That’s very powerful. For cloud native developers like myself who are used to working with container images as the deliverable artifact, this makes that workflow very easy. Podman is included. You can create entire development environments at will that are totally “pure”: no side effects because everything you need is in the container. That’s a Dev Container.




  • For what it’s worth, I just wrote up a compose.yaml file as I’d write it for Docker Compose and it just worked. See the bottom of my comment on this GitHub issue for an example. I think the team’s intention is for it to transparently support whatever you’d write for a standard Compose file but of course we don’t have things like the brand new Docker watch. They do point to the Compose spec in the Podman Compose README. Bind mounts are good enough for me, thus far.