![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
I use tiddlywiki for my single-user wiki. The setup is dead simple, one html file on your computer you open directly. There is also a nodejs server implementation, which I use.
I use tiddlywiki for my single-user wiki. The setup is dead simple, one html file on your computer you open directly. There is also a nodejs server implementation, which I use.
Pihole reloading in my case is probably mostly slow because of the hardware. That signal functionality to reload is pretty neat, though I think I disagree with the config files being the only thing specifying the servers behaviour exactly being a big advantage. In an environment using infrastructure as code it would probably be better to define DNS over the generic nsupdate API (e.g. with ansible or other equivalent tools) than having to write custom code to reload some config files that have to be regenerated every time. But for smaller home setups both options are probably fine anyhow.
Does this support DNS management with nsupdate? I’m currently automating DNS on pihole by changing a text file and reloading the service, which is just not very convenient not to mention slow.
I know that header files have some pretty horrible issues with templates and cyclic dependencies and so on, but from an organisational perspective I really like them. If I have to implement some complicated algorithm I could easily have a thousand likes + of Code, but the header still quite nicely shows the general structure in one or two screens. Whenever I do classes in python I start wishing for headers at like 300 lines, simply because I loose track of all the functions I already made.
Maybe I’m just not a good python programmer tho.