marsokod

Ouch, and that is with Gitea and Codeberg being essentially the same software.

You can easily do that with forgejo/gitea. However, you cannot sync these issues, that’s a one-off operation.

You can however totally sync the git repo - either out of the box or using web hooks/git hooks.

I have been using Bookstack, I like it though it is missing a few features I would love:

• you cannot insert a video in it
• there is no possibility to comment on a particular text
• the permissions management is only done with roles. That’s fine generally but I wanted to be able to share a specific page with a specific user, and for that I had to basically create a dedicated role for this use.

You cannot really hide it. The launch has to be public to warn airplanes and ships so they can avoid the area. And once the launch is public, such a failure is quite evident to anyone who was interested in following it, so you might has well publish the news instead of trying to hide the unhidable.

By quantity of oil, I would think an oil spill is more damaging.

However, the damage from the sum of all oil spills pale in comparison to the damage of burned fossil fuels. But that’s because we try not to spill oil too much, that’s expensive to waste it.

Defense money is not lost, it pays people within your country. And you can even decide whether it goes to big corps or small companies.

Sorry, my autocorrect changed its into it’s.

Overlay it with a map of electricity emissions and it will fit nicely with a few small exceptions (like any small country neighbouring Poland, they will have bad air regardless of their own production).

https://app.electricitymaps.com/map

Tailscale surprisingly was the fastest, even faster than plain Wireguard, despite being userspace. But it also consumed more memory (245 MB after the iperf3 test!) and CPU.

Do we know if this is a variation due to the test protocol or Tailscale is using wireguard with specific settings to improve, slightly, its speed?

One thing to keep in mind is that the websocket sync is not straightforward to set up with vaultwarden and the proxy. If you don’t have it working, then your client does not necessarily sync on every change.

Maybe this is related to this, with sync not being performed by the client you were using for modification?

If you are in an enterprise environment, it is easier to sell Ubuntu - at least there is a company that can provide support for it behind. Companies want to make sure someone is on the hook to fix an issue that would be blocking to them, and this is much harder with something like Debian.

That’s why Red Hat is used that much in companies, and what Canonical main revenues are coming from.

But as a selfhoster, I use Debian by default for my servers. Only if there is a very specific need for Ubuntu would I switch, and I am frankly tired of the Snap shenanigans on my desktop (thinking of migrating to PopOS or KDE Neon).

I don’t know if there is any specific utilities for that. You can always export your settings and reimplement them in lldap: this should be doable with a python script.

I never really understand why LDAP was so complicated. There must be needs in big setups that I am aware of but strangely I always found it not intuitive.

Yes, same for me. On android DAVx5 is perfect, and on MacOS, iOS there is native support. For Linux and Windows, your mileage may vary (fairly easy on Linux but very different variations and some require additional software).

It supports a proper sync (my wife’s shared events do show up on my phone and I can modify them there) and the address book is specific to each user by default, but you can create shared address books as well. Again, that is synced two ways.

For LDAP, by default nextcloud only reads it. But you can enable LDAP writing as well.

I do this with nextcloud (and lldap for the user management). Though that could probably be overkill for just contacts and calendars.

If you use the linuxserver.io image, as of last month yes. They migrated to everything updated through the docker container.

I’ll provide an ELI5, though if you actually want to use it you’ll have to go beyond ELI5.

You contact a web service via a combination of IP address and port. For the sake of simplicity, we can assume that domain name is equivalent to IP address. You can then compare domain name/port with street name/street number: you need both to actually find someone. By default, some street numbers are really standard, like 443 is for regular encrypted connection. But you can have any service on any street number, it’s just less nice and less standard. This is usually done on closed networks.

Now what happens if you have a lot of services and you want all of them reachable at address 443? Well basically you are now in the same situation as a business building with a lobby. Whenever you want to contact a service, you go to 443, ask the reception what floor they are in, and they will direct you there. The reception desk is your proxy: just making sure you talk to the right people.

If you don’t care about GPIO/serial lines, frankly buy a small NUC or a used Thinkcentre M93p. Used, you can find them for very cheap (£100 in my case), they are powerful enough for your needs, you can have an actual SSD storage, and you will avoid the odd issue with a software not working on ARM (less and less the case but still worth taking into account).