Add wireguard dependency note #750
Closed
Conversation
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
Changes to intro/product summary blurb made to follow Marketing messaging guidelines. Link at top no goes to product page of the foundries.io website. Note that other requested changes which involve the sidebar, header, or footer will be handled in a separate PR. QA: Ran linkcheck and viewed built HTML. This commit addresses FFTK-3449 Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Added to ``apt`` command to install dependencies. QA Steps: Checked that the package name is correct, checked rendered output. Ran linkcheck. No issues found. This commit addresses FFTK-3454, "Documentation: Wireguard dependency" Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
|
Docs for 85aa42b are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2759/docs/artifacts/html/index.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness
Overview
Adds a dependency reported by customer.
Checklist
make linkcheck.-s, --signoff).-S, --gpg-sign).