mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 00:45:19 +00:00
Update links to documentation (#4163)
* update links to documentation * revert .sailsrc change * fix broken link
This commit is contained in:
parent
df87e8e4b6
commit
9af92b23aa
2
.github/ISSUE_TEMPLATE/bug-report.md
vendored
2
.github/ISSUE_TEMPLATE/bug-report.md
vendored
@ -33,4 +33,4 @@ assignees: ''
|
||||
|
||||
<!-- If this is an issue with the Fleet UI: Please also [answer this question](https://github.com/fleetdm/fleet/blob/main/CONTRIBUTING.md#6-is-this-an-issue-with-the-fleet-ui). -->
|
||||
|
||||
<!-- If this is a performance issue: Please [follow these steps](https://github.com/fleetdm/fleet/blob/main/docs/01-Using-Fleet/06-Monitoring-Fleet.md#debugging-performance-issues) to generate and attach a debug archive. -->
|
||||
<!-- If this is a performance issue: Please [follow these steps](https://fleetdm.com/docs/using-fleet/monitoring-fleet.md#debugging-performance-issues) to generate and attach a debug archive. -->
|
||||
|
@ -141,7 +141,7 @@ You can also do this by setting the `targets` field in the [YAML configuration f
|
||||
|
||||
## How do I automatically assign a host to a team when it enrolls with Fleet?
|
||||
|
||||
[Team enroll secrets](https://github.com/fleetdm/fleet/blob/main/docs/01-Using-Fleet/10-Teams.md#enroll-hosts-to-a-team) allow you to automatically assign a host to a team.
|
||||
[Team enroll secrets](./10-Teams.md#enroll-hosts-to-a-team) allow you to automatically assign a host to a team.
|
||||
|
||||
## Why my host is not updating a policy's response.
|
||||
|
||||
|
@ -34,7 +34,7 @@ const options = [
|
||||
label: "Documentation",
|
||||
onClick: () =>
|
||||
window.open(
|
||||
"https://github.com/fleetdm/fleet/blob/main/docs/README.md",
|
||||
"https://fleetdm.com/docs",
|
||||
"_blank"
|
||||
),
|
||||
},
|
||||
|
@ -36,7 +36,7 @@ const UserMenu = ({
|
||||
label: "Documentation",
|
||||
onClick: () =>
|
||||
window.open(
|
||||
"https://github.com/fleetdm/fleet/blob/main/docs/README.md",
|
||||
"https://fleetdm.com/docs",
|
||||
"_blank"
|
||||
),
|
||||
},
|
||||
|
@ -199,7 +199,7 @@ const TeamManagementPage = (): JSX.Element => {
|
||||
<p>
|
||||
Want to learn more?
|
||||
<a
|
||||
href="https://github.com/fleetdm/fleet/blob/main/docs/01-Using-Fleet/10-Teams.md"
|
||||
href="https://fleetdm.com/docs/using-fleet/teams"
|
||||
target="_blank"
|
||||
rel="noopener noreferrer"
|
||||
>
|
||||
|
@ -98,7 +98,7 @@ The goal of quality assurance is to catch unexpected behavior prior to release:
|
||||
|
||||
### Collecting bugs
|
||||
|
||||
All QA steps should be possible using `fleetctl preview`. Please refer to [docs/03-Contributing/02-Testing.md](https://github.com/fleetdm/fleet/blob/main/docs/03-Contributing/02-Testing.md) for flows that cannot be completed using `fleetctl preview`.
|
||||
All QA steps should be possible using `fleetctl preview`. Please refer to [docs/03-Contributing/02-Testing.md](https://fleetdm.com/docs/contributing/testing) for flows that cannot be completed using `fleetctl preview`.
|
||||
|
||||
Please start the manual QA process by creating a blank GitHub issue. As you complete each of the
|
||||
flows, record a list of the bugs you encounter in this new issue. Each item in this list should
|
||||
|
@ -232,7 +232,7 @@ Yes! Orbit is licensed under an MIT license and all uses are encouraged.
|
||||
|
||||
### How does orbit update osquery? And how do the stable and edge channels get triggered to update osquery on a self hosted Fleet instance?
|
||||
|
||||
Orbit uses a configurable update server. We expect that many folks will just use the update server we manage (similar to what Kolide does with Launcher's update server). We are also offering [tooling for self-managing an update server](https://github.com/fleetdm/fleet/blob/main/docs/02-Deploying/04-fleetctl-agent-updates.md) as part of Fleet Premium (the subscription offering).
|
||||
Orbit uses a configurable update server. We expect that many folks will just use the update server we manage (similar to what Kolide does with Launcher's update server). We are also offering [tooling for self-managing an update server](https://fleetdm.com/docs/deploying/fleetctl-agent-updates) as part of Fleet Premium (the subscription offering).
|
||||
|
||||
## Community
|
||||
|
||||
|
@ -12,7 +12,7 @@ func WriteExpiredLicenseBanner(w io.Writer) {
|
||||
w,
|
||||
"Your license for Fleet Premium is about to expire. If you’d like to renew or have questions about "+
|
||||
"downgrading, please navigate to "+
|
||||
"https://github.com/fleetdm/fleet/blob/main/docs/01-Using-Fleet/10-Teams.md#expired_license and "+
|
||||
"https://fleetdm.com/docs/using-fleet/teams#expired_license and "+
|
||||
"contact us for help.",
|
||||
)
|
||||
// We need to disable color and print a new line to make it look somewhat neat, otherwise colors continue to the
|
||||
|
@ -10,4 +10,4 @@ Simply install `fleetctl` with `npm install -g fleetctl`.
|
||||
|
||||
## Usage
|
||||
|
||||
See the [fleetctl documentation](https://github.com/fleetdm/fleet/blob/main/docs/01-Using-Fleet/02-fleetctl-CLI.md) or `fleetctl --help` for usage instructions.
|
||||
See the [fleetctl documentation](https://fleetdm.com/docs/using-fleet/fleetctl-CLI) or `fleetctl --help` for usage instructions.
|
||||
|
Loading…
Reference in New Issue
Block a user