Fixes for Millau-Rialto Deployment (#493)

* Expose two nodes publicly through brucke.link

* Use flags for GNU `sed` instead of BSD `sed`

* Update Substrate relay entrypoint scripts to initialize bridge

* Add Rialto to Millau relay to Compose deployment

* Stop initializing Rialto chain through chainspec

* Include logging for Substrate pallet

* Make Rialto to Millau entrypoint executable

* Use YAML references for relay components

* Use published Substrate Relay image

* Relay messages from Millau to Rialto

* Use Bob nodes to serve message lane

* Fix some port number issues for PoA-Rialto deployment

* Stop directly referencing `environment` anchor in nodes

* Add probable cause to relayer error message

* Edit monitoring config file in-place

* Add some sleep time between bridge init call and starting relays

* Expose grafana.

* Use Root key as bridge pallet owner

In our case that's going to be Alice since she's Root for our Dev
and Local chains.

Co-authored-by: Tomasz Drwięga <tomasz@parity.io>

bridges/bin/rialto/node/src/chain_spec.rs

@@ -157,7 +157,11 @@ fn testnet_genesis(
 		pallet_grandpa: Some(GrandpaConfig {
 			authorities: Vec::new(),
 		}),
-		pallet_substrate_bridge: load_millau_bridge_config(),
+		pallet_substrate_bridge: Some(BridgeMillauConfig {
+			// We'll initialize the pallet with a dispatchable instead.
+			init_data: None,
+			owner: Some(root_key.clone()),
+		}),
 		pallet_sudo: Some(SudoConfig { key: root_key }),
 		pallet_session: Some(SessionConfig {
 			keys: initial_authorities
@@ -183,10 +187,3 @@ fn load_kovan_bridge_config() -> Option<BridgeKovanConfig> {
 		initial_validators: rialto_runtime::kovan::genesis_validators(),
 	})
 }
-
-fn load_millau_bridge_config() -> Option<BridgeMillauConfig> {
-	Some(BridgeMillauConfig {
-		init_data: None,
-		owner: Some([0; 32].into()),
-	})
-}