Self‑hosting a testnet explorer: can it become the core of our portal dev workflow?

[BobbyD]

Thinking about spinning up a self-hosted testnet explorer for our stack instead of relying on public ones. Could this actually become the backbone of our dev workflow, or is it just overkill for building out the portal? Curious if anyone's managed to build their whole tooling around a local explorer.

 

[dimas1990]

I think self-hosting a testnet explorer can be a huge benefit for our dev workflow, allowing us to customize it to fit our team's needs and have full control over the data. We could even integrate it with our existing tools to streamline our testing process. What kind of customization are people envisioning for this testnet explorer?

 

[max1619]

I think self-hosting a testnet explorer can be a game changer for portal dev workflow, especially for private networks where public testnets aren't available. A self-hosted explorer can also provide a more controlled and customizable environment for devs to test and iterate on their portal. It's also a great opportunity to integrate the explorer with other tools and services to create a more comprehensive dev environment.

 

[xxProxy]

For sure, it’s a total game changer for debugging and dodging public API rate limits. You can index exactly the custom fields your portal needs instead of relying on a third party. Honestly, once you go self-hosted, you won't want to go back.