Skip to content

Commit 7b81f5a

Browse files
authored
Merge pull request #1662 from aaryanporwal/master
Added description for the .gitignore file
2 parents 94375e5 + 45a8f7a commit 7b81f5a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

en/deploy/README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,9 @@ db.sqlite3
4949
And save it as `.gitignore` in the "djangogirls" folder.
5050

5151
> **Note** The dot at the beginning of the file name is important! If you're having any difficulty creating it (Macs don't like you to create files that begin with a dot via the Finder, for example), then use the "Save As" feature in your editor; it's bulletproof. And be sure not to add `.txt`, `.py`, or any other extension to the file name -- it will only be recognized by Git if the name is just `.gitignore`.
52+
Linux and MacOS treat files with a name that starts with `.` (such as `.gitignore`) as hidden
53+
and the normal `ls` command won't show these files.
54+
Instead use `ls -a` to see the `.gitignore` file.
5255

5356
> **Note** One of the files you specified in your `.gitignore` file is `db.sqlite3`. That file is your local database, where all of your users and posts are stored. We'll follow standard web programming practice, meaning that we'll use separate databases for your local testing site and your live website on PythonAnywhere. The PythonAnywhere database could be SQLite, like your development machine, but usually you will use one called MySQL which can deal with a lot more site visitors than SQLite. Either way, by ignoring your SQLite database for the GitHub copy, it means that all of the posts and superuser you created so far are going to only be available locally, and you'll have to create new ones on production. You should think of your local database as a good playground where you can test different things and not be afraid that you're going to delete your real posts from your blog.
5457
@@ -229,4 +232,3 @@ Once you have a few posts created, you can go back to your local setup (not Pyth
229232

230233

231234
Give yourself a *HUGE* pat on the back! Server deployments are one of the trickiest parts of web development and it often takes people several days before they get them working. But you've got your site live, on the real Internet!
232-

0 commit comments

Comments
 (0)