Support custom Blockfrost API URL in provider configuration #481
Description
Is your feature request related to a problem? Please describe.
Currently, Atlas only supports the default Blockfrost API endpoint for provider configuration. This limits users who want to connect to self-hosted or alternative Blockfrost-compatible endpoints.
Describe the solution you'd like
I would like Atlas to support specifying a custom Blockfrost API URL in its provider configuration. When a custom URL is provided, Atlas should use it for all Blockfrost API interactions.
The newest release of blockfrost-haskell adds support for custom Blockfrost URLs, making this feature straightforward to implement in Atlas.
Describe alternatives you've considered
- Continuing to use only the default Blockfrost endpoint (not flexible for private deployments).
- Forking and modifying Atlas locally (not maintainable long-term).
Additional context
This feature will enable integration with private Blockfrost deployments like dolos.