update unfurler and build config
This commit is contained in:
		
							parent
							
								
									fdbca80920
								
							
						
					
					
						commit
						79e2883ebe
					
				| @ -131,8 +131,8 @@ export NVM_DIR="${HOME}/.nvm" | ||||
| source "${NVM_DIR}/nvm.sh" | ||||
| 
 | ||||
| # what to look for | ||||
| frontends=(mainnet liquid onbtc) | ||||
| backends=(mainnet testnet testnet4 signet liquid liquidtestnet onbtc) | ||||
| frontends=(mainnet liquid onbtc bitb) | ||||
| backends=(mainnet testnet testnet4 signet liquid liquidtestnet onbtc bitb) | ||||
| frontend_repos=() | ||||
| backend_repos=() | ||||
| 
 | ||||
|  | ||||
| @ -15,7 +15,7 @@ screen -dmS x startx | ||||
| sleep 3 | ||||
| 
 | ||||
| # start unfurlers for each frontend | ||||
| for site in mainnet liquid onbtc;do | ||||
| for site in mainnet liquid onbtc bitb;do | ||||
|     cd "$HOME/${site}/unfurler" && \ | ||||
|     echo "starting mempool unfurler: ${site}" && \ | ||||
|     screen -dmS "unfurler-${site}" sh -c 'while true;do npm run unfurler;sleep 2;done' | ||||
|  | ||||
| @ -281,6 +281,26 @@ export const networks = { | ||||
|         routes: routes.lightning.routes, | ||||
|       } | ||||
|     } | ||||
|   }, | ||||
|   bitb: { | ||||
|     title: 'BITB | Bitwise Bitcoin ETF', | ||||
|     description: 'BITB provides low-cost access to bitcoin through a professionally managed fund', | ||||
|     fallbackImg: '/resources/bitb/bitb-preview.jpg', | ||||
|     routes: { // only dynamic routes supported
 | ||||
|       block: routes.block, | ||||
|       address: routes.address, | ||||
|       tx: routes.tx, | ||||
|       mining: { | ||||
|         title: "Mining", | ||||
|         routes: { | ||||
|           pool: routes.mining.routes.pool, | ||||
|         } | ||||
|       }, | ||||
|       lightning: { | ||||
|         title: "Lightning", | ||||
|         routes: routes.lightning.routes, | ||||
|       } | ||||
|     } | ||||
|   } | ||||
| }; | ||||
| 
 | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user