iac
/
docker-elk
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Remove unnecessary prompt symbol in console cmds 

This forces users to manually remove the symbol after copying commands
using GitHub's inline copy button.
This commit is contained in:
Antoine Cotten 2023-03-18 00:08:09 +01:00
parent 5f497953f9
commit 907a0703d8
No known key found for this signature in database
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@ -134,8 +134,8 @@ git clone https://github.com/deviantony/docker-elk.git
Then, start the stack components locally with Docker Compose: Then, start the stack components locally with Docker Compose:
```console ```sh
$ docker-compose up docker-compose up
``` ```
> **Note** > **Note**
@ -172,16 +172,16 @@ reset the passwords of all aforementioned Elasticsearch users to random secrets.
The commands below reset the passwords of the `elastic`, `logstash_internal` and `kibana_system` users. Take note The commands below reset the passwords of the `elastic`, `logstash_internal` and `kibana_system` users. Take note
of them. of them.
```console ```sh
$ docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user elastic docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user elastic
``` ```
```console ```sh
$ docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user logstash_internal docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user logstash_internal
``` ```
```console ```sh
$ docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user kibana_system docker-compose exec elasticsearch bin/elasticsearch-reset-password --batch --user kibana_system
``` ```
If the need for it arises (e.g. if you want to [collect monitoring information][ls-monitoring] through Beats and If the need for it arises (e.g. if you want to [collect monitoring information][ls-monitoring] through Beats and
@ -209,8 +209,8 @@ reset the passwords of all aforementioned Elasticsearch users to random secrets.
1. Restart Logstash and Kibana to re-connect to Elasticsearch using the new passwords 1. Restart Logstash and Kibana to re-connect to Elasticsearch using the new passwords
```console ```sh
$ docker-compose up -d logstash kibana docker-compose up -d logstash kibana
``` ```
> **Note** > **Note**
@ -246,8 +246,8 @@ Elasticsearch data is persisted inside a volume by default.
In order to entirely shutdown the stack and remove all persisted data, use the following Docker Compose command: In order to entirely shutdown the stack and remove all persisted data, use the following Docker Compose command:
```console ```sh
$ docker-compose down -v docker-compose down -v
``` ```
### Version selection ### Version selection
@ -372,8 +372,8 @@ users][builtin-users]), you can use the Elasticsearch API instead and achieve th
In the example below, we reset the password of the `elastic` user (notice "/user/elastic" in the URL): In the example below, we reset the password of the `elastic` user (notice "/user/elastic" in the URL):
```console ```sh
$ curl -XPOST -D- 'http://localhost:9200/_security/user/elastic/_password' \ curl -XPOST -D- 'http://localhost:9200/_security/user/elastic/_password' \
-H 'Content-Type: application/json' \ -H 'Content-Type: application/json' \
-u elastic:<your current elastic password> \ -u elastic:<your current elastic password> \
-d '{"password" : "<your new password>"}' -d '{"password" : "<your new password>"}'