Add guide for hosting your own instance of Blockstack Connect

[markmhendrickson]

Ahead of sunsetting the hosted versions of the Blockstack Browser (see stacks-archive/blockstack-browser#2072) and Blockstack Connect (see leather-wallet/extension#970), the UserX team would like to publish a guide for any developer who would like to spin up their own hosted instance of the latter and configure their app to use it.

This guide will be relevant to any developer that chooses to continue relying on Blockstack Connect instead of upgrading to the newer Stacks Wallet (e.g. because mobile is critical and it's not yet supported).

The guide would need to take the user roughly through these steps:

1. Pull the latest version of Blockstack Connect from GitHub
2. Configure it given target domain (if needed?)
3. Deploy to domain (perhaps with recommended host instructions e.g. Netlify?)
4. Configure app to use new domain instead of app.blockstack.org

We would link to this guide from a blog piece explaining the hosted sunsets in general, recommending that developers upgrade to the Stacks Wallet in time, and providing this Blockstack Connect provisioning route as an alternative for those who don't want to use the Stacks Wallet.

This guide should emphasize that Hiro PBC will no longer support the Blockstack Connect codebase at all, even for critical patches. So the developer assumes full responsibility for maintenance and future feature development.

[markmhendrickson]

@aulneau Is this something you could help by providing the base instructions material, given your familiarity with Blockstack Connect? Or might someone else on the team be best to help in that regard?

@pgray-hiro could then take this material and revise it in preparation for publish.

cc @andresgalante

[markmhendrickson]

@andresgalante @aulneau let's discuss carving out time to get this drafted. It's been hanging out in the backlog for awhile now.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed. Please reopen if needed.