The decision to keep both names is strange though. If its just a name and colour theme, what is the point? Thunderbird already has far more brand recognition, so it makes sense to just switch.

Would be awesome if they provided a pre-built container for each module, but understand it'd create a very large number of builds for them, and then people would want module+module which would create an exponentional number of possibilities.

Maybe an all modules build and the ability to toggle them via ENV?

We've used it in a single-user (a docker user) and multi-user (user for each dev) environment.

Most, if not all, containers work fine, there are some, like mailcow which don't work well with it.

If you have multiple IPs on the one machine, there is a longstanding bug that means you can't bind the same port on different IPs. Eg IP1:80 and IP2:80. The workaround for this is separate rootless docker users + runtime for each container that shares ports, nasty.

In a multi-user environment we simply setup rootless docker under each devs user, so they have their own runtime and their own containers isolated from other devs. This works really well.

Overall it works well for us.

I asked it what it's knowledge cutoff was, and it said 2021-09.

Anyone know why it's trained on such old data?

I don't ever do anything illegal, I just don't like being tracked.

  curl -o docker-compose.yaml https://raw.githubusercontent.com/makeplane/plane/master/deploy/selfhost/docker-compose.yml
  curl -o .env https://raw.githubusercontent.com/makeplane/plane/master/deploy/selfhost/variables.env
  vim .env # adjust for your environment
  docker compose up -d

Some other notable docker-based projects that I've seen require an .sh are Sentry [1] and Postal [2].