Updated `## Persist the todo data` section (#13434)

* Updated `## Persist the todo data` section

I provided a 3-step procedure from lines 81 to 102 on how to access the container's shell environment, since It was unclear how to access the `/etc/todos` directory. Also, nowhere, in the tutorial, was it mentioned that containers are *self-contained shell environments*. This information is crucial for beginners following along with the tutorial.

Take care.

* Second update

This update was due to a suggestion provided by @thaJeztah .
This commit is contained in:
Michael Šòdéké 2021-09-02 09:01:34 -07:00 committed by GitHub
parent 83d1fb372b
commit ac1df4d6a9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -76,7 +76,7 @@ There are two main types of volumes. We will eventually use both, but we will st
## Persist the todo data
By default, the todo app stores its data in a [SQLite Database](https://www.sqlite.org/index.html){:target="_blank" rel="noopener" class="_"} at
`/etc/todos/todo.db`. If you're not familiar with SQLite, no worries! It's simply a relational database in
`/etc/todos/todo.db` in the container's filesystem. If you're not familiar with SQLite, no worries! It's simply a relational database in
which all of the data is stored in a single file. While this isn't the best for large-scale applications,
it works for small demos. We'll talk about switching this to a different database engine later.