The original EverQuest theme song was mine. Captured the epic wide-eyed wonder of going on an adventure perfectly.
I run Guix System on my personal laptop and Project Bluefin on my work machine.
Guix is even easier to get started with now thanks to the Guix Packager , a web UI for writing Guix package definitions.
Project Bluefin auto-updates thanks to its use of container images deliver system updates. It's also just a great platform to get started writing containerized apps, since it ships with rootless Podman by default and you can easily add new developer tools using just
commands.
The Intel discrete cards are fantastic value for money. There's plenty of folks on the internet who can attest to this. Intel's support story in general (so not just graphics cards) on Linux has been nothing less than sterling. If you're using any Linux kernel you can expect Intel stuff to just work. It's been this way for at least a decade.
WebOS powers TVs now and, from the article, Amazon intends this replacement to cover their Fire tablet line. WebOS ticks all their boxes, especially since apps in Amazon's new flavor are intended to be delivered as React Native web apps.
I'm devastated they didn't choose to pick up webOS for this.
If you're looking for the GitLab version of Codeberg's hosted Forgejo Git forge, there's Framagit hosted by Framasoft.
This sounds like something on your end as I get cached builds every time, rootlessly even. Podman also supports cache mounts.
Check my comment history for an example of a simple bind mount compose.yaml
I use for developing a small Python project. It's exactly the same as Docker Compose (since Podman Compose follows the Compose spec) but if you're just getting started, it might be a good skeleton to build on.
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.
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?