toc, how-to/deploy: add deploying TiDB using TiUP (#2198) #2199
Conversation
This file contains hidden or 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
* how-to/deploy: add delopying TiDB using TiUP * how-to: update wording * add the remaining part * remove chinese content * media: add two images * remove chinese code comments * how-to: fix a link * make anchor links valid * how-to: make wording consistent * fix a link * media: add one login image * media: add a dashboard image * media: fix an image name * update content Co-authored-by: yikeke <yikeke@pingcap.com>
5 tasks
sre-bot
added
priority/P1
yikeke
approved these changes
Apr 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #2198 to release-4.0
What is changed, added or deleted? (Required)
/how-to/deploy/orchestrated/about deploying TiDB using TiUPTOC.mdWhich TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?