Docker - Duniter wrapper + Entrypoint can survive a config / peers.db loss

Duniter wrapper

/usr/bin/duniter is a script again which does the very minimum so that the duniter command can work from anywhere and without and with --home parameter. the default Duniter home is /var/lib/duniter, but a different one can be set with --home <new_home>.

Survive a config loss

When conf.json is not found and a peer node is defined as DUNITER_SYNC_HOST or DUNITER_PEER_HOST, bootstrap a new conf.json file with the blockchain parameters from this node.

This is enough for duniter to survive a config loss with no need for a full resync.

Survive a peers.db loss

When peers.db is not found and a peer node is defined as DUNITER_SYNC_HOST or DUNITER_PEER_HOST, bootstrap a new peers database using sync --only-peers against this node.

Auto sync against a chunks folder

It is now possible to autosync against a chunks folder from a dex export. It only needs these settings:

• DUNITER_AUTO_SYNC=true
• DUNITER_SYNC_HOST=<path_to_chunks_folder>
• DUNITER_PEER_HOST=<node_to_get_peers_from>

changed the description

@pini-gh review effectuée :)

changed the description

added 4 commits

• 893c25d7 - build(docker): WORKDIR = Duniter home
• c364820a - build(docker): entrypoint: use 'set -uo pipefail'
• 4bba966c - build(docker): bootstrap conf.json and peers.db
• 57780c75 - ref(docker) home_default -> profile_default

Compare with previous version

resolved all threads

@librelois Les modifs ont été faites.

added 1 commit

• 92d5949d - doc(docker): fix volume /etc/duniter description

Compare with previous version

Je refais une tentative de fix pour la description du volume /etc/duniter dans la doc pour docker. On verra bien...

resolved all threads

resolved all threads

resolved all threads

resolved all threads

resolved all threads

approved this merge request

review ok: y a plus qu'a tester :)

@pini-gh les 2ème et 3ème commit qui ne modifient que l'entrypoint, devrait être de type feat.

Aussi, sache que je suis en train de migrer peers.db dans une db rust située dans data/dunp_v1_sled.

D'ici la semaine prochaine peers.db n'existera plus, donc ton script ne fonctionnera plus.

requested review from @librelois

assigned to @pini-gh and unassigned @librelois

unassigned @pini-gh

added 3 commits

• 6ee1efac - feat(docker): bootstrap conf.json and peers.db
• a1a1848e - ref(docker) home_default -> profile_default
• 2cfbe630 - doc(docker): fix volume /etc/duniter description

Compare with previous version

Pour le deuxième non, pas du tout. C'est du lint en toute rigueur.

On a pas de type lint, ce que s'en rapproche le plus est un type style, c'est le type que j'utilise pour tout ce qui est formatage et fix des warnings du linter, mais ce type de commit ne doit pas impacter le comportement à l'exécution.

Ici ton 2ème commit impacte le comportement à l'exécution, le comportement sera plus strict et remontera donc mieux certaines erreurs qui pouvait être silencieuses avant, c'est donc bien une feature, il faut donc utiliser le type feat ;)

added 4 commits

• 6169dffb - feat(docker): entrypoint: use 'set -uo pipefail'
• 2587a56e - feat(docker): bootstrap conf.json and peers.db
• bd218453 - ref(docker) home_default -> profile_default
• 1ed8dc98 - doc(docker): fix volume /etc/duniter description

Compare with previous version

resolved all threads

mentioned in commit 28fa91de

merged