GitDeployHub

fuellabs/bridge-integration-tests

github.com/fuellabs/bridge-integration-tests ↗
Node.js API
16 environment variables found in .env.example

Set these on your host before deploying. Each platform has an “Environment Variables” section in the deploy flow.

  • HTTP_ETHEREUM_CLIENT General environment variables note: The same private keys can be used for the different roles if desired note: HTTP_DEPLOYER can be left…
  • HTTP_DEPLOYER
  • HTTP_FUEL_CLIENT
  • PK_ETH_DEPLOYER
  • PK_ETH_SIGNER1
  • PK_ETH_SIGNER2
  • PK_FUEL_DEPLOYER
  • PK_FUEL_SIGNER1
  • PK_FUEL_SIGNER2
  • FUEL_CHAIN_CONSENSUS_ADDRESS Settlement layer contract deployments
  • FUEL_MESSAGE_PORTAL_ADDRESS
  • FUEL_ERC20_GATEWAY_ADDRESS
  • FUEL_FUNGIBLE_TOKEN_ADDRESS secret ERC-20 testing variables note: if these variables are left blank then the script will create these contracts and report back their…
  • ETH_ERC20_TOKEN_ADDRESS secret
  • FUEL_GAS_LIMIT (Optional) Fuel network specific variables
  • FUEL_GAS_PRICE
Alternative Fly.io Anything Dockerized — requires the Fly CLI.
macOS
brew install flyctl && fly launch --from https://github.com/fuellabs/bridge-integration-tests
Linux
curl -L https://fly.io/install.sh | sh && fly launch --from https://github.com/fuellabs/bridge-integration-tests
Windows (PowerShell)
iwr https://fly.io/install.ps1 -useb | iex; fly launch --from https://github.com/fuellabs/bridge-integration-tests
Or deploy to a different host
← Try another repo