Skip to content

Commit

Permalink
Add notes
Browse files Browse the repository at this point in the history
  • Loading branch information
jason-fox committed Dec 18, 2023
1 parent 47430dd commit 007c0e8
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,8 @@ the repository:
Where `<command>` will vary depending upon the databases we wish to activate. This command will also import seed data
from the previous tutorials and provision the dummy IoT sensors on startup.

> :information_source: **Note:** If you want to clean up and start over again you can do so with the following command:
> [!NOTE]
> If you want to clean up and start over again you can do so with the following command:
>
> ```console
> ./services stop
Expand Down Expand Up @@ -690,7 +691,8 @@ The `postgres-db` container is driven by environment variables as shown:
| POSTGRES_USER | `postgres` | Username for the PostgreSQL database user |
| POSTGRES_DB | `postgres` | The name of the PostgreSQL database |

> :information_source: **Note:** Passing the Username and Password in plain text environment variables like this is a
> [!NOTE]
> Passing the Username and Password in plain text environment variables like this is a
> security risk. Whereas this is acceptable practice in a tutorial, for a production environment, you can avoid this
> risk by applying [Docker Secrets](https://blog.docker.com/2017/02/docker-secrets-management/)

Expand Down Expand Up @@ -1102,7 +1104,8 @@ mysql-db:
- 'MYSQL_ROOT_HOST=%'
```
> :information_source: **Note:** Using the default `root` user and displaying the password in an environment variables
> [!NOTE]
> Using the default `root` user and displaying the password in an environment variables
> like this is a security risk. Whereas this is acceptable practice in a tutorial, for a production environment, you can
> avoid this risk by setting up another user and applying
> [Docker Secrets](https://blog.docker.com/2017/02/docker-secrets-management/)
Expand Down

0 comments on commit 007c0e8

Please sign in to comment.