feat: iroh-one

[Arqu]

Based off of the awesome work @fabricedesre did on #188

Took it a little bit further in terms of making it mergeable for us and reducing the maintenance burden of the crate.

@fabricedesre Hope this is a nice middle ground that works for all.

• uds support remains, it's feature enabled now at compile time
• I've dropped the racing http/p2p work and we can do that as a separate piece with a custom ContentLoader as @dignifiedquire suggested
• made the cleanups I mentioned over there.
• Dropped the android hard coded bits (mainly the uds socket definition) however you can pass it in as an argument (actually need to finish this - done)

LMK what y'all think

[dignifiedquire]

what exactly is this used for?

[Arqu]

It's just a convenience function to copy the top level rpc_client configuration (with the mem addresses) across the sub configs.

[Arqu]

@fabricedesre just to clarify some of the stuff here. I don't think we can take on the android specific code you had, but I've aimed to give enough flexibility so that it's an easy setup. I assume that you don't have the luxury of cli arguments when starting things on android thus relying on defaults.

If that is the case I think the best way to support this is by having iroh-one being flexible and configurable enough that you can simply import it as a crate in your own rust project and simply copy over just the main.rs and slightly modify it to fit your needs. Think for this specific case, it would be enough to simply modify the config with the correct uds path before setting the rpc client.

[fabricedesre]

@Arqu I can actually use cli arguments in my case (it's not regular android either), but I dislike having a mix of configuration through cli args and in a config file. If I can use --cfg and have all the configuration in a config file that's ideal.

[Arqu]

@Arqu I can actually use cli arguments in my case (it's not regular android either), but I dislike having a mix of configuration through cli args and in a config file. If I can use --cfg and have all the configuration in a config file that's ideal.

Oh that's really nice to hear! I'll test it out today/tomorrow and report back, should be already set up or pretty close to it.

[Arqu]

@fabricedesre confirming that --cfg=path/to/your/config works

Sample toml config

gateway_uds_path = 'tmp.sock'

[gateway]
writeable = false
fetch = false
cache = false
port = 9051
denylist = false

[gateway.headers]
access-control-allow-headers = 'content-type, content-disposition, last-modified, cache-control, accept-ranges, etag, service-worker, x-ipfs-gateway-prefix, x-trace-id, x-content-type-options, x-ipfs-path, x-ipfs-roots'
access-control-allow-methods = 'GET, PUT, POST, DELETE, HEAD, OPTIONS'
accept-ranges = 'none'
access-control-allow-origin = '*'
cache-control = 'no-cache, no-transform'

[store]
path = 'iroh-store-db'

[p2p.libp2p]
listening_multiaddr = '/ip4/0.0.0.0/tcp/4444'
bootstrap_peers = [
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN',
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa',
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb',
    '/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt',
    '/ip4/104.131.131.82/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ',
]
mdns = false
kademlia = true
autonat = true
relay_server = true
relay_client = true
gossipsub = true
max_conns_out = 256
max_conns_in = 256
max_conns_pending_out = 256
max_conns_pending_in = 256
max_conns_per_peer = 8
notify_handler_buffer_size = 256
connection_event_buffer_size = 256
dial_concurrency_factor = 16

Remember to build with --feature=uds-gateway to enable uds support.

If this is ok with you I'd like to move towards merging this?

[fabricedesre]

looks great, thanks!