Chapter 3 - Persisting Data#2
Open
clairefro wants to merge 2 commits intochapter-2-validating-requestsfrom
Open
Chapter 3 - Persisting Data#2clairefro wants to merge 2 commits intochapter-2-validating-requestsfrom
clairefro wants to merge 2 commits intochapter-2-validating-requestsfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To prevent losing all of our restaurants every time our server restarts, and to allow our API to scale to be used by multiple clients at once, we need to add a real database.
For this example, we added MongoDB. However, you can use any type of database you want (PostgreSQL, MySQL etc).
IMPORTANT - handling secrets
When dealing with databases, we almost always have secrets we don't want to share with the public that give access to our data. To hide secrets, such as the database connection URI, you will need to make a local file at your project root called
.env. This file is explicitly ignored fromgittracking because we added it to the.gitignorefile. That means the contents of the.envfile will not show up anywhere you publish your code, like GitHub. Secret's safe!The variables defined in your
.envwill be local only to your computer. When you go to deploy your API to the public internet, your hosting service will let you define your environment variables secretly and securely from their dashboard.