worldofgeese

joined 1 year ago
[–] [email protected] 4 points 10 months ago* (last edited 10 months ago)

There's real usability benefits too. I've collected some anecdotes from Reddit:

Rootless podman is my first choice for using containers now, it works fantastically well in my experience. It's so much nicer to have all my container related stuff like volumes, configs, the control socket, etc. in my home directory and standard user paths vs. scattered all over the system. Permission issues with bind mounts just totally disappear when you go rootless. It's so much easier and better than the root privileged daemon.

and,

If you are on Linux, there is the fantastic podman option "--userns keep-id" which will make sure the uid inside+the container is the same as your current user uid.+

and,

Yeah in my experience with rootless you don't need to worry about UID shenanigans anymore. Containers can do stuff as root (from their perspective at least) all they want but any files you bind mount into the container are still just owned/modified by your user account on the host system (not a root user bleeding through from the container).

finally,

The permissions (rwx) don't change, but the uid/gid is mapped. E.g. uid 0 is the running user outside the container, by uid 1 will be mapped to 100000 (configurable), and say 5000 inside the container is mapped to 105000. I don't remember the exact mapping but it works roughly like that.

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago) (1 children)

I try to write about it as much as I can here! There's also [email protected]

[–] [email protected] 2 points 10 months ago

For something simple that just needs a bind mount like

services:
  app:
    build:
      context: .
      target: base
    volumes:
      - ./debaser_studio:/opt/app-root/src/debaser_studio/debaser_studio
    ports:
      - "3000:3000"
      - "8000:8000"
    user: default

I haven't found any issues. Do you have more complex needs?

[–] [email protected] 2 points 10 months ago

I use Logseq for everything. I've found the more you throw into it the more useful it becomes since your touch points are so frequent and that gets you thinking through and exploring your graph more. I've yet to use any of the data query features but I've heard they're incredibly powerful.

Whiteboards are just a fantastic way for modeling a topic or themes you know you want to turn into a deliverable when the how is uncertain.

[–] [email protected] 5 points 10 months ago* (last edited 10 months ago) (3 children)

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
[–] [email protected] 2 points 10 months ago

You'd have to ask them. There's a link to their Matrix server on the website.

[–] [email protected] 1 points 10 months ago (2 children)

According to their website, Cyberia Club is

A kind and amazing hacker collective centered in Minnesota, with global friends.

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago)

I did a little research and found a Redditor who was able to answer better than me:

Logseq makes it easier to work with blocks, transclusions can be edited in place, and you can automatically be building another page consisting of blocks you’re writing in your daily journal or another page.

EDIT: I was really curious about the major differences and what is enabled by Logseq's block-based architecture so I asked my network on Mastodon and got some great answers!

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago)

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.

[–] [email protected] 2 points 10 months ago (3 children)

Logseq is block-based. Each bullet is a block. This is very powerful because it allows you to interlink concepts, ideas, at the level of the block vs page.

[–] [email protected] 3 points 10 months ago (1 children)

You can use Git, Syncthing or any other FOSS sync tool of your choice.

[–] [email protected] 5 points 10 months ago (3 children)

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.

view more: ‹ prev next ›