By some sheer coincidence, I searched this topic today. I’ve been a consistent user of the parenthesis expansion, but never thought of why I preferred one or the other.

I suppose the primary advantage is that $() will expand in a consistent way. You can even nest quotes and more expansions in one, while you’d struggle the same with backtick notation.

So I’ll just keep using parentheses.

Exuvia

Cool find!

In addition to podman unshare (which you would just prefix in front of commands like chmod), you can just temporarily do podman unshare chown -R root: <path> if you backup while the container is down. Don’t try that command on live containers.

For a more permanent solution, you can investigate which user (ID) is the default in the container and add the option --user-ns=“keep-id:uid=$the_user_id”. This does not work with all images, especially those that use multiple users per container, but if it works, the bind mount will have the same owner as the host.

To find the user ID, you can run podman exec <container> id. In most of the images I use, it’s usually 1000.

I haven’t looked much into the differences, but from my brief research, it appears that Forgejo has just recently updated such that migration from Gitea is no longer possible. I knew that they had become a “hard” fork last year but it has now diverged.

From a feature standpoint, I know that Forgejo is working on Fediverse integration. Beyond that, I think the differences are less apparent.

So to answer your question, I use Gitea and have for a long time. They’ll still remain MIT-licensed even if it’s no longer fully open source. However, the owning company can (and may) cease open source development. If I had known of Forgejo breaking away earlier, or if I were a new user, I would have probably started with Forgejo. That’s my recommendation.

Absolutely! I have used multiple origins for posting my projects to Gitea/Forgejo and GitHub. You can also mirror repositories from one site to another, too, although it requires a clean slate for pulling from another remote.

The biggest use case for me is documenting (as code) my home network setup on my private forge.

You may or may not be a developer, but I would like to vote for Gitea/Forgejo. Should you ever get a grasp of git, a git forge is great for keeping code and even plain text documents recorded. It’s my favorite self-hosted service by far.

It can even operate as an OIDC server, so you can create a single login for all your services (that support OIDC).

I’ll also recommend Grist, an alternative to Google Sheets (and Notion, I believe?). It’s a web interface to spreadsheets that supports Python code as formulas. (I’ve also tried Nocodb, another Notion alternative, and I much prefer Grist.)

I’m not from the UK (or the Commonwealth) but I had some of these books as a child. Loved them. Thanks for posting this.

Incredible yet accurate analogy

If you’re using git to version Caddy configuration, you can use a pre-commit hook to test it, ensuring that you’ll never have invalid configuration. That’s what I do.

caddy validate

There’s some extra command args that may be necessary but that should be an adequate first step.

Epic divested itself of Bandcamp last year. I’ll continue supporting artists that way

Hopefully the new maintainer can get releases going again. It’s a great extension!

If you’re talking about the extension that looks like an R with a green arrow, the author passed away a couple years ago. https://github.com/einaregilsson/Redirector/issues/329

The repo has a new maintainer but there’s been no new releases since the maintainer doesn’t have access to the extension release pages. No surprise that a MV3 version hasn’t been worked on.

It still works on Firefox, though.