haproxy Settings for Blockscout.com
Blockscout.com uses haproxy for all BlockScout hosted and external instances.
If you would like to add your instance to Blockscout.com, make the required changes and submit a PR to https://github.com/blockscout/haproxy-config
Instructions
Blockscout uses two-part path names for network urls:
the first part (org
) designates the organization/type of the network,
the second part (netname
) names the network.
For example:
Eth mainnet:
https://blockscout.com/eth/mainnet
(org=eth
,netname=mainnet
)Ethereum Classic mainnet:
https://blockscout.com/etc/mainnet
(org=etc
,netname=mainnet
)Kovan testnet:
https://blockscout.com/eth/kovan
(org=eth
,netname=kovan
)
1. Add a new org
for your blockscout instance's url
org
for your blockscout instance's url1) Add a new acl
under the #Check for network type section in the cfg file.
2) Add a corresponding exception !is_myorg
to the #default redirect section
3) add !is_myorg
to every line in the #redirect for networks section
2. Add a new acl with your netname
In the #Check for network name section add a new acl
with your netname
similar to existing ones
3) Set the cookie and name of rpc/websockets servers
4. Add new backend sections to the end of the file
Add new backend_mynet
and backend_mynet_ws
sections to the end of the file and provide dns names of your BlockScout instances.
For example:
Change the following parameters to match your specific case
backend mynet
:acl is_...
reqirep ...
http-request set-header Host ...
server mynet_server...
- don't forget to specify port 443 here
backend mynet_ws
:http-request set-header Host...
http-request set-header Origin ...
don't forgethttps
hereserver mynet_server...
- don't forget port 443 here
Submit a PR to the configuration repo at https://github.com/blockscout/haproxy-config
Last updated