kiol

Exactly

The write up is detailed, but the fact is that Vikunja does not support customization of their self-hosted platform. If you tried it, you’ll have definitely noticed. It is worthy of discussion, especially for those of us enthusiasts explicitly wanting to “own” our platform identities through self-hosting. Isn’t that exactly why we use Lemmy and self-hosting?

For dokuwiki, I’ve found I can safely edit many menus by copying them from /inc to /conf. So far, so good.

For dokuwiki, I’ve copied wiki/inc/lang/en/ over to conf/lang/en for then applying edits

Thanks for the suggestion. In this case, I’ve running directly from systemctl --user space. Realizing I was directly editing the files, when I should have copied them out of their default directories to avoid them being overwritten.

I’ve begun making numbers of small edits to wording displayed and such across many of my applications, because I find myself engaging with multiple types of people: those with accounts, those who are hyper technical, and those randomly browsing around with no account.

I’ve noticed that system defaults from developers often have no bearing on my actual users, so embracing my ability to customize to taste. :)

Also running Nginx at home, with declarative config files. Most people I know are on traefik. Is it running well for you at this point?

Which IR hat were you using? Guess I’m not aware of MorphOS.

Did you consider doing the “mount a small monitor” style stats dashboard in your home?

I occasionally spin up Octoprint, and Klipper, on a Pi Zero W.

I’m working on building out a wiki that will flow according to skill level. Still early days, but working on it.

Seems tuwunel is dev of previous project and this is community fork.

You can always change the name on your instance. Agree that there is no reason to use the project name, especially in this case.

You can selfhost discovery, no problem. docs.syncthing.net/users/stdiscosrv.html