This is kinda the same idea but made for what you originally asked for: https://garagehq.deuxfleurs.fr/

I think there was a Nextcloud plugin that allowed doing that. If you run that anyways, worth a try.

Hostile not quite, as it was a group of core developers. But still a shitty move, especially how it was done in secrecy and disregarding other devs and the larger community.

Hosting a signal proxy is probably not a big deal if you don’t plan to ever travel to countries that have blocked Signal, but I would strongly advise against hosting a Tor exit node as a private individual. Tor is used for criminal activities all the time, and unless you have plausible deniability as an organization (and a good lawyer), it will be blamed on you personally.

I wondered about this before but apparently the Telegram client is terrible spaghetti code under the hood, making these kind of ideas not feasible.

You might like Monocles Chat though, which is an Android XMPP client with a somewhat nicer looking interface.

There is also the work in progress Moxxy client, which is a from ground up new XMPP client written in Flutter. It seems to take some interface inspiration from Telegram, but to be honest, it isn’t anywhere near to be fully usable and development has been slow in recent months.

In terms of raw CPU power, you will rarely have issues with anything newer than 10 years old. But some built in video conversion hardware can differ significantly and power consumption is usually also lower for newer CPUs.

Afaik it uses a very similar codebase and plugins can be easily ported or might even work out of the box.

Maybe this? https://theia-ide.org/

Only once during the initial setup, afterwards its all managed by Systemd. Once you know about it, it takes like one minute max.?

Its actually much easier to autostart containers with Podman, as it has full Systemd integration, so you can handle them like any other service. All you need to do is write a simple .container file for the Podman built-in Quadlet service, which closely follows the normal Systemd .service file syntax.

There are .pod files for Quadlet now, which do what you want. No Kubernetes involved.

My impression is really the opposite. Podman is constantly being improved and nice features get added all the time.

If you don’t like SELinux, just disable it. Nothing to do with Podman.

Podman-generate was replaced by Quadlet .container files, which works better.

And a Pod also has it’s own virtual network, why manually create one?

Currently at step 9. Waiting for the roving bands of thugs to arrive 😅

Gitlab’s main advantage is the tight integration with CI/CD and a web based IDE. But it has some annoying limitations in the non-enterprise version.

Forgejo is great, but it comes with only community support.

You can get commercial support from the Gitea project (from which Forgejo forked off), but if that is something important for you, Gitlab has probably also better commercial support structures in place.

??? The location and the file name of the certificates don’t change, so why would I have to do that?

On the contrary, before I disabled the certbot’s Nginx integration, every three months certbot would “manage” to break my Nginx and I had to manually repair it.

I think we are not talking about the same thing. I mean the Certbot extension that automatically modifies the Nginx config files. A telltale sign are usually the comments "#managed by certbot” that it likes to leave behind all over your config files.

I switched to Dehydrated (with dns-01 challenge), but Certbot itself is fine, the problem is the Nginx integration that tries to automatically change your Nginx config files.

You usually want less integration, not more. Simple self-contained things. Nginx is good at that. That’s also why you don’t want to use Nginx Proxy Manager or Certbot’s Nginx integration etc. It first looks like they make it easier, but there is too much hidden complexity under the hood.

Also, sooner or later you will run into some software that you would really like to try, which is only documented for Nginx and uses some sort of image caching or so, that is hard to replicate with Caddy etc.

For 2.: use dns-01 challenge to generate wildcard SSL certs. Saves so much time and nerves.

That’s what everyone thinks for a while, and then they go back to Nginx.

Small Form Factor I guess.