Holochain Conductor Config Files?

Greetings Friends,

How to run an app using the main holochain conductor? (Not using hc)

Up to now I have been using hc sandbox commands but now I want to deploy using the full holochain conductor as part of my work for HoloNET (.NET/Unity client) where the conductor will be fully embedded/integrated.

Also, why is the hc.exe 9.6MB and holochain.exe is 45MB?! (On Windows)

That’s quite a big jump! What is is the holochain.exe doing that hc.exe doesn’t?! lol :slight_smile:

Many thanks,

Ok, I managed to get the main holochain conductor running and it created my config file, but I noticed it generates 2? Each has different settings in it, seems the main one is here:

C:\Users\david\AppData\Roaming\holochain\0.0.143\conductor-config.yaml (with lots more settings in it) and then there is another one here:

C:\Users\david\AppData\Roaming\holochain\holochain\config\conductor-config.yml which only seems to have settings for the database in it?

C:\Users\david\AppData\Roaming\holochain\holochain\config\conductor-config.yml looks like this:

environment_path: “C:\Users\david\AppData\Roaming\holochain\holochain\data\databases”
type: lair_server_legacy_deprecated
keystore_path: ~
danger_passphrase_insecure_from_config: default-insecure-passphrase
dpki: ~
admin_interfaces: ~
network: ~
db_sync_strategy: Fast
and C:\Users\david\AppData\Roaming\holochain\0.0.143\conductor-config.yaml looks like this:

environment_path: “C:\Users\david\AppData\Roaming\holochain\0.0.143\conductor”
type: lair_server
connection_url: “named-pipe:\.\pipe\SMXWCEKnTk8i1WdzEJbjT?k=yj6c7AymhGhW50ct6Cmis9_SYbtlGjnthBMypUbxm0M”
dpki: ~

  • driver:
    type: websocket
    port: 18764
    • type: proxy
      type: quic
      bind_to: ~
      override_host: ~
      override_port: ~
      type: remote_proxy_client
      proxy_url: “kitsune-proxy://f3gH2VMkJ4qvZJOXx0ccL_Zo5n-s_CnBjSzAsEHHDCA/kitsune-quic/h/–”
      bootstrap_service: “https://bootstrap.holo.host/
      gossip_strategy: sharded-gossip
      gossip_loop_iteration_delay_ms: “1000”
      gossip_outbound_target_mbps: “1.5”
      gossip_inbound_target_mbps: “1.5”
      gossip_historic_outbound_target_mbps: “0.4”
      gossip_historic_inbound_target_mbps: “0.4”
      gossip_peer_on_success_next_gossip_delay_ms: “60000”
      gossip_peer_on_error_next_gossip_delay_ms: “300000”
      gossip_local_sync_delay_ms: “60000”
      gossip_dynamic_arcs: “true”
      gossip_single_storage_arc_per_space: “false”
      default_rpc_single_timeout_ms: “30000”
      default_rpc_multi_remote_agent_count: “3”
      default_rpc_multi_remote_request_grace_ms: “3000”
      agent_info_expires_after_ms: “1200000”
      tls_in_mem_session_storage: “512”
      proxy_keepalive_ms: “120000”
      proxy_to_expire_ms: “300000”
      concurrent_limit_per_thread: “4096”
      tx2_quic_max_idle_timeout_ms: “30000”
      tx2_pool_max_connection_count: “4096”
      tx2_channel_count_per_connection: “2”
      tx2_implicit_timeout_ms: “30000”
      tx2_initial_connect_retry_delay_ms: “200”
      danger_tls_keylog: no_keylog
      disable_publish: “false”
      network_type: quic_bootstrap
      db_sync_strategy: Fast
      So it looks like the first shorter one is a global one for all versions of the conductor sharing the same database?

And the 2nd longer one is separate configs per conductor version?

Sorry, just trying to understand more how the actual conductor works… :slightly_smiling_face: Is there any more documentations I can look at for this? Such as explanations for the config files, etc? Thanks.

I also can’t see how I tell the conductor what hApp to run? I presume it must be a setting in the config somewhere? Thanks :slight_smile: