Add PROVIDER_HTTP_URL and PROVIDER_WS_URL to setup wizard #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The StarkNet staking package's entrypoint script requires
PROVIDER_HTTP_URLandPROVIDER_WS_URLenvironment variables to connect to StarkNet full nodes (like Juno), but these were not configurable through the DAppNode setup wizard. Users could only rely on hardcoded values from the sepolia variant, making it impossible to customize provider endpoints for mainnet deployments.Solution
This PR adds the missing provider URL configuration fields to the setup wizard, allowing users to specify their StarkNet full node endpoints during package installation.
Changes Made
setup-wizard.yml:
provider_http_urlfield mapping toPROVIDER_HTTP_URLenvironment variableprovider_ws_urlfield mapping toPROVIDER_WS_URLenvironment variablehttp://juno.public.dappnode:6070/v0_8andws://juno.public.dappnode:6071/v0_8)docker-compose.yml:
PROVIDER_HTTP_URL: ""andPROVIDER_WS_URL: ""environment variables to the staking serviceCompatibility
The sepolia variant continues to work unchanged since it has its own docker-compose.yml with predefined URLs that override the setup wizard values. This ensures existing sepolia deployments are unaffected while enabling mainnet customization.
User Experience
Users will now see two additional setup fields during installation:
Both fields come with working defaults but can be customized for different StarkNet full node configurations.
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.