De-dupe configs and systemd units between docs and source code about bitbox-base HOT 3 CLOSED

This issue has become obsolete due to creating the config files from tempaltes with bbbconfgen, see #160

• config files are now no longer inline
• the cannot be easily integrated into the documentation, however, as they are created on the fly

For the moment, the docs are maintained manually.

from bitbox-base.

create some templated .md files with placeholder values for the actual config contents

similar how the wlan0.conf is done (with {wpa-ssid} and {wpa-psk})?

from bitbox-base.

create some templated .md files with placeholder values for the actual config contents

similar how the wlan0.conf is done (with {wpa-ssid} and {wpa-psk})?

Yeah, exactly. The concrete .md files can be rendered by some preprocessor script, inserting the actual configs where placeholders like {bitcoin-conf} are. We could run those preprocessors on CI to assert that the .md files are in sync with what would be generated from the templates.

from bitbox-base.