-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "docs: parachain onboarding locally"
- Loading branch information
1 parent
d19db2e
commit c13f4cb
Showing
10 changed files
with
897 additions
and
535 deletions.
There are no files selected for viewing
Binary file not shown.
17 changes: 17 additions & 0 deletions
17
pop-cli-for-appchains/guides/deploying-your-parachain-to-polkadot/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
description: The following are guides on how to launch your parachain on Polkadot. | ||
--- | ||
|
||
# Launching your Parachain on Polkadot | ||
|
||
A typical development workflow for launching your parachain on Polkadot:  | ||
|
||
* Run your parachain **locally** using Pop CLI.  | ||
* Under the hood, Pop CLI launches your parachain to Paseo Local TestNet automatically for development purposes: | ||
* [Run your parachain on Paseo](../running-your-parachain.md) | ||
* When ready to test your parachain in a live environment with other parachains: | ||
* Use [this guide](../running-on-paseo-locally.md) to mimic the manual onboarding process for Paseo TestNet locally.  | ||
* When comfortable with manually onboarding locally, then use the next guide to onboard to Paseo Live TestNet. | ||
* [Launching your parachain on Paseo TestNet](../launching-your-parachain-on-polkadot/launching-on-paseo.md) | ||
* Finally, when thoroughly tested on Paseo, launch on Polkadot | ||
* The process here is similar to launching on Paseo. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.