runfalk

It's pretty easy to create one yourself (from an open MR https://github.com/containers/toolbox/pull/483/files#diff-21...), but it would have been nice to have out of the box.

I've used buildah to set up a C/C++ dev environment in a Ubuntu toolbox at work without any major issues.

It's also used by certbot, pyjwt, ckan, proxy.py, scrapy, etc. The list is pretty long but I do agree with you that the majority of packages neither use nor should use it.

https://github.com/zopefoundation/Zope/network/dependents?de...

Glad you like it! Don't worry too much as we currently have a workaround. Their SDK still allows us to build kernel modules but the installation experience now requires manually switching the package post installation to allow root access .

This of course assumes that Synology doesn't remove this option before DSM 7 is released.

I've had a less than stellar experience with their support too. I'm the author of a reasonably popular WireGuard plugin (https://github.com/runfalk/synology-wireguard) and in the next DSM version they are basically breaking all kernel module plugins without a migration path. A kind user has found a workaround and made a PR, but Synology have no interest in helping out with this (https://github.com/runfalk/synology-wireguard/issues/66#issu...).

Shameless plug: If you want a static site generator with an admin UI I can recommend Lektor (https://www.getlektor.com/). You declare your data model and templates and Lektor serves an editing UI for you. There is a good video introduction by Armin Ronacher (original author) if you prefer to digest video content: https://www.youtube.com/watch?v=lTWTCwuPdrU

Disclaimer: Occasionally I moonlight as a maintainer of Lektor.

A task queue or message queue is generally used to delegate jobs to worker processes.

Imagine you are GitHub and a user comments on an issue that has 1000 people participating. As soon as the user makes a comment you want to send an email to every user that there are new comments.

The straight forward way is to do that in the web application when the comment is posted, but that takes a lot of time and leaves the commenter staring at a loading screen until everyone is notified. (There are other reasons as well)

With a message/task queue you would create 1000 messages (each saying "send e-mail about this issue to this user"). Then you have worker processes that in a loop look at one message at a time and sends an e-email. When the message is sent the worker marks (acks) that message as handled and it is removed from the message/task queue.

Four years ago I open sourced version 0.1 of this project. Previously is was part of my company's workshift management system. Over the years I've slowly improved it and added functionality to simplify common use cases.

Happy to answer any questions!