-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace references to clarinet integrate
with clarinet devnet start
#624
replace references to clarinet integrate
with clarinet devnet start
#624
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ryanwaits!
In terms of consistency and even SEO, I think we should encourage the use of "Devnet" instead of naming.
Also, the "devnet" can be ran in the Platform, in which case it's not "local"
I think we need to do a pass on the deployment plan documentation as well but maybe in an other PR
@@ -1,20 +1,20 @@ | |||
--- | |||
title: Clarinet Integrate | |||
title: Local Development Environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we include the word Devnet
in the title?
@@ -105,6 +105,11 @@ module.exports = [ | |||
label: 'Run a local testing environment', | |||
id: 'clarinet/guides/clarinet-integrate', | |||
}, | |||
{ | |||
type: 'doc', | |||
label: 'Run an integration environment', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be "devnet" instead of "integration envrionment"
What does this PR do?
clarinet integrate
with the newclarinet devnet start
clarinet integrate
on older versions in faq