refactor: docker setup for local web3; dev env with local web3

[dnechay]

Issue tracking

Part of #3053
Follow up to #3360

Context behind the change

Here we removed scripts folder in favor of common docker setup. Now when developing smart contracts, sdk or subgraph engineer either can keep writing unit tests or writing all the infra locally by yarn docker:web3-up from the project root (docs updated with some hints).

To distinguish between local environment and testnet - there are now two different env files:

• .env is expected to be used for running services in docker and pointing to testnet
• .env.local is expected to be used for running services locally (i.e. in terminal) and pointing to localhost web3
  The above expectation is reflected in "setup scripts", i.e. setup-kv-store.ts and setup-staking.ts for oracles.

Also updated yarn setup:local command for convenience. If env files are correctly filled and web3 is running - it will perform staking for oracle and fill its KV store.

Note

.env.local takes precedence over .env for both backend and frontend apps, so if you have both - running from terminal will rely on .env.local, but in docker context we ignore these files so keep relying only on .env inside of docker containers.

How has this been tested?

• run yarn docker:web3-up from project root and check that blockchain node and subgraph run correctly
• follow steps from e2e test using local node section of human-protocol/subgraph README; make sure graph is deployed and works correctly by running local-node script from human-protocol/sdk multiple times
• run yarn setup-local for oracles, check KV store values via local Subgraph UI
• run ./scripts/fortune-all-local.sh, make sure everything is started and operational; press Ctrl+C and ensure processes properly shut down

Important

When press Ctrl+C multiple times - only kill commands will ignore it, when for yarn ... commands that shutdown docker it propagates, so take this into account and not press it mindlessly, otherwise you will have to manually cleanup containers and volumes.

Release plan

Just merge.

Potential risks; What to monitor; Rollback plan

No

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

5 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
faucet-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jun 2, 2025 0:17am
faucet-server	⬜️ Ignored (Inspect)	Visit Preview		Jun 2, 2025 0:17am
human-app	⬜️ Skipped (Inspect)			Jun 2, 2025 0:17am
human-dashboard-frontend	⬜️ Skipped (Inspect)			Jun 2, 2025 0:17am
staking-dashboard	⬜️ Skipped (Inspect)			Jun 2, 2025 0:17am

[flopez7]

Looks good!