TerribleDev/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typos. Clarify tasker configuration.

Browse Source
This commit is contained in:
Ross McDonald
2018-04-19 11:09:08 -05:00
parent 7ea3f3c53f
commit 19c9f17022
2 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
articles/enterprise/components/exporter.md
View File

@@ -209,4 +209,4 @@ successful issuing an `HTTP GET` request to the root (`/`) endpoint:
curl -v http://localhost:3031/
```
If the Exporter was installed and configured properly, you will receive an `HTTP 200` reponse back.
If the Exporter was installed and configured properly, you will receive an `HTTP 200` response back.

11
articles/enterprise/components/tasker.md
View File

@@ -5,7 +5,7 @@ The **Tasker** component runs scheduled and on-demand tasks for the Stoplight pl
> #### Networking Details
>
> The default port for the Tasker component is TCP port **9432**. This port can
> be customzied via configuration variable.
> be customized via configuration.
>
> Tasker must be able to receive incoming connections from the following components:
>
@@ -105,7 +105,8 @@ TASKER_MODE="shell"
#### CORE_ROOT
The `CORE_ROOT` denotes the absolutel path to stoplight-hub-builder package root.
The `CORE_ROOT` denotes the absolute path to the stoplight-hub-builder package
root.
```
CORE_ROOT="/opt/stoplight-hub-builder"
@@ -166,8 +167,8 @@ Be sure to customize any variables as needed to match your environment
### Docker
To expose these to the Docker runtime, either write them to a file and use the
`--env-file` argument:
To expose configuration variables to the Docker runtime, either write them to a
file and use the `--env-file` argument:
```bash
cat <<EOF>tasker-env-vars
@@ -227,4 +228,4 @@ curl -v http://localhost:9432/health
```
If Tasker was installed and configured properly, you will receive an `HTTP 200`
reponse back.
response back.