Maybe you can set it up for them? It’s really the easiest way + it does not cost anything that’s not paid for already anyways (electricity and an Internet connection).

You can selfhost MediaWiki usingntheir official Docker image.

https://hub.docker.com/_/mediawiki

There will always be this one asshole of a coworker who happily name-dropping you in a conference call with the project owner.

That’s the downside, yes.

Write an ungodly large amount of code-comments - up to a point where you add 20 lines of explanations to a 6 lines long function where two lines are variables assignments.

Source code is for humans to read. The compiler ignores the comments.

Yep! The functionality for performing arithmetic expressions this way is called “arithmetic expansion”.

2.6.4 Arithmetic Expansion

Arithmetic expansion provides a mechanism for evaluating an arithmetic expression and substituting its value. The format for arithmetic expansion shall be as follows:

$((expression))

The expression shall be treated as if it were in double-quotes, except that a double-quote inside the expression is not treated specially. The shell shall expand all tokens in the expression for parameter expansion, command substitution, and quote removal.

Next, the shell shall treat this as an arithmetic expression and substitute the value of the expression. […]

https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_06_04

That is a posixly correct method to do arithmetic expressions.

unit-test: passed

I gave up Bash scripting. I explicitly do “shell scripting” now, where “shell” is implied to be a POSIX compliant shell of any type.

They do it since quite some time now, right?

but I’d like to give Nginx Proxy Manager a try, it seems easier to manage stuff not in docker.

NPM is pretty agnostic. If it receives a request for a specific address and port combination it just forwards the traffic to another specific address and port combination. This can be a docker container, but also can be a physical machine or any random URL.

It also has Let’s Encrypt included (but that should be a no-brainer).

I run my website as static site from within a Docker container, I wonder how I would get the information about the other containers into that site.

Do you directly serve that site from the host or do you run the script and write something in a volume the site has read access to or bind a file?

Do you guys have any suggestions?

Because I don’t like software getting in my way I just cobbled together some HTML and CSS and call it a day.

Usually you just see LibreOffice and nothing else, so it’s fine, I guess. Not a web-based editor, but usable.

Ah, I see. Not as native web application, though.

They’re using Alpine Linux, install X and Openbox and Xvnc and serve KasmVNC via Nginx and connect via KasmVNC to that X instance. LibreOffice is started in fullscreen and looks like a slightly blurry web application.

But in reality it is just a regular desktop installation with some extra things.

@fikran@lemm.ee, maybe this is a solution? I wouldn’t recommend it because it’s not really a web-based document editor.

So, LibreOffice can be used over the Internet in a web browser?

Exactly. With directly using certbot handling all and everything fully automatically I ran my old setup with a free dyndns subdomain for quite some time without any issues.

Since Let’s encrypt nowadays is basically implemented in every reverse proxy: certificates are an absolute no-brainer.

If someone manages to buy and configure a domain to serve selfhosted content, this person will also be able to either set up certbot or use the built-in functionality of their reverse proxy.

It’s 2025. Not having “real certificates” is something admins intentionally do. Since there is Let’s Encrypt available, all other solutions for non-paid certificates are obsolete.

Keep them memorized. The old tools just work, even if MICROS~1 tries to hide them and replace them with useless crap apps.

There – of course – won’t be a singular official source stating “Hey guys, we’re open core now”. You need to put this together bit-by-bit.

Here are some links for research

• Official statement on the takeover
• Gitea Enterprise/Gitea Cloud hiding features behind a cloud solution and a paywall which makes Gitea itself open-core
• Open Letter to the new Gitea owners with a summary and a reply, signed by a lot of Gitea devs and FOSS scene people.
• As @gratux@lemmy.blahaj.zone mentioned: A fork under the name Forgejo was done due to new Gitea owners did not care much about the concerns. (Started as asoft-fork but with 10.0 it became a hard fork.)
• Gitea owners made it mandaroy to remove copyright headers and set the corporation as copyright holder. Here, here, and here