TW

while I agree that plaintext passwords in configs aren't very safe(*), I don't see how a keyring is helpful for a service that is usually started automatically at boot time...

what i meant is that you already HAVE a man page, so it exists, but is a bit long.

it's just a rst file, see an example there: https://bitbucket.org/thomaswaldmann/moin-2.0/src/f6ee7dd9f400befc5a70af07fdfb688f07df45c4/docs/man/?at=default https://bitbucket.org/thomaswaldmann/moin-2.0/src/f6ee7dd9f400befc5a70af07fdfb688f07df45c4/docs/conf.py?at=default#cl-223

I didn't look at dyndnsc stuff recently, but for borgbackup we have some code in setup.py that makes a set of usable length man pages (~ per subcommand). https://github.com/borgbackup/borg/blob/1.1.3/setup.py#L451

I personally use and administer debian/ubuntu systems, but did not build or submit packages yet. But I need them, so I would volunteer except somebody more experienced can and would...

i just have tried to build a .deb, but ran into some issues: a) it seems that the script "dyndnsc" needs to have another name than the package "dyndnsc", because...

Currently playing around with the MQTT enabled firmware, but already run into a problem: The device was previously joined to a WiFi (so it does not open its own AP...

I'ld guess for a simple implementation that would be also the way to go with `borg-import` importing such backups. With **a lot** of effort one could theoretically maybe avoid that...

@m3nu do you know how to fix this easily? I did some web search, but didn't find a solution. Just noticed that `brew test-bot` seems to be popular within such...

Still broken: ``` Run brew audit --strict borgbackup-fuse.rb Warning: audit is a developer command, so Homebrew's developer mode has been automatically turned on. To turn developer mode off, run: brew...