feat: create config automatically if not provided

[SgtPooki]

Title

feat: create config automatically if not provided

Description

• splits and organizes some of the code in src/index.ts
• adds new configuration creation step if --config is not provided when starting up.
  • creates new convention for ~/.config/amino directory for storing configuration files

Notes & open questions

• Any better suggestions for config path or file name?
  • updated to ~/.config/amino as the root. may update further?
• Do we want to change defaults in example-config.json?
• Do we want to use this chance to update config file to use more direct js-libp2p config name instead of the Kubo convention?

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[SgtPooki]

self review

[achingbrain]

https://stackoverflow.com/questions/47819464/where-to-save-configuration-data-files-on-gnu-linux suggests storing config under ~/.config because it's what XDG has specified and seems popular?

.js-libp2p as a directory name seems like a bit of an overreach, perhaps ~/.config/amino/config.json?

[SgtPooki]

stackoverflow.com/questions/47819464/where-to-save-configuration-data-files-on-gnu-linux suggests storing config under ~/.config because it's what XDG has specified and seems popular?

Will update

.js-libp2p as a directory name seems like a bit of an overreach, perhaps ~/.config/amino/config.json?

Maybe ~/.config/amino/js-config.json in order to not squat on the namespace? but i'll push an update for this

[SgtPooki]

Maybe ~/.config/amino/js-config.json in order to not squat on the namespace? but i'll push an update for this

~/.config/amino/bootstrapper.json would probably be better?

[achingbrain]

Also, let's use jsonc-parser or some other jsonc parser so we can have comments in our config files..

Maybe ~/.config/amino/js-config.json in order to not squat on the namespace?

We're already squatting on the binary name, so just ~/.config/amino/config.json didn't seem like a terrible location 😉

[SgtPooki]

FYI @achingbrain we do have ~/.config/@libp2p from your protocol-adventure tool. do we want to re-use that?

[achingbrain]

Oh yeah, maybe we'd be better internet citizens if we did that.

If we use the module name then ~/.config/@libp2p/amino-dht-bootstrapper/config.json would be the one I suppose?

[SgtPooki]

self review

[2color]

Do we want to use this chance to update config file to use more direct js-libp2p config name instead of the Kubo convention?

I think this is a good idea. I imagine that most users of this are coming from js-libp2p, for which it would more intuitive to follow js-libp2p config naming.

[SgtPooki]

self review

[SgtPooki]

@achingbrain @2color this is ready for review again: merged from main and updated config to use js-libp2p config keys. One non-normal item in the config is the identity property

[2color]

I would add the full list of defaults also used by Helia:

    '/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN',
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb',
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt',

    // va1 is not in the TXT records for _dnsaddr.bootstrap.libp2p.io yet
    // so use the host name directly
    '/dnsaddr/va1.bootstrap.libp2p.io/p2p/12D3KooWKnDdG3iXw9eTFijk3EWSunZcFi54Zka4wmtqtt6rPxc8',
    '/ip4/104.131.131.82/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ'

https://github.com/ipfs/helia/pull/649/files#diff-1b64c902120625f3cd192eb7b8f10b323c4952735118b52ed87098ab4f7a6526R4-R10

[SgtPooki]

addressed in #201

[2color]

LGTM

[2color]

I took the liberty of pushing some small fixes.

Overall, looks great and makes it much easier to run without much prior knowledge,

[github-actions]

🎉 This PR is included in version 1.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀