Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/advanced/APP_INSTALL.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ App installation can be done a variety of ways: either through a file/directory

* [Volume-mount app directory](#volume-mount-app-directory)
* [Download via URL](#download-via-url)
* [Multiple apps](@multiple-apps)
* [Multiple apps](#multiple-apps)
* [Apps in distributed environments](#apps-in-distributed-environments)

## Volume-mount app directory
Expand All @@ -27,7 +27,7 @@ We can bind-mount this upon container start and use it as a regular Splunk app:
$ docker run -it -v ./splunk_app_example:/opt/splunk/etc/apps/splunk_app_example/ --name so1 --hostname so1 -p 8000:8000 -e "SPLUNK_PASSWORD=<password>" -e "SPLUNK_START_ARGS=--accept-license" -it splunk/splunk:latest
```

You should be able to view the `splunk_app_example` in SplunkWeb after the container successfully finished provisioning.
You should be able to view the `splunk_app_example` in SplunkWeb after the container successfully finished provisioning.x
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the extra x here?


## Download via URL
In most cases, you're likely hosting the app as a tar file somewhere accessible in your network. This decouples the need for Splunk apps and configuration files to exist locally on a node, which enables Splunk to run in a container orchestration environment.
Expand Down