adelorenzo/getting-started
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Merge pull request #65 from mattlevan/patch-1

Browse Source 
Fix slightly snide comment about SQLite
This commit is contained in:
Stefan Scherer 2020-07-08 18:13:24 +02:00 committed by GitHub
commit 3641a64e81
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/tutorial/persisting-our-data/index.md
View File

@ -74,7 +74,7 @@ There are two main types of volumes. We will eventually use both, but we will st
By default, the todo app stores its data in a [SQLite Database](https://www.sqlite.org/index.html) at By default, the todo app stores its data in a [SQLite Database](https://www.sqlite.org/index.html) 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`. 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, 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 an actual database engine later. it works for small demos. We'll talk about switching this to a different database engine later.
With the database being a single file, if we can persist that file on the host and make it available to the With the database being a single file, if we can persist that file on the host and make it available to the
next container, it should be able to pick up where the last one left off. By creating a volume and attaching next container, it should be able to pick up where the last one left off. By creating a volume and attaching