Issues related to heroku-push on Windows
Use lazy evaluated ForeignKey references to prevent future problems

Starting with Django 1.7 there have been multiple people hitting #django
with problems that eventually could be solved using lazy references to
related models instead of class references. Teaching it this ways seems
to be a good way to prevent future issues.
note the difficulty of deployment chapter, fixes #139
Updated code_editor/README.md

Atom is nowadays available pre-built for Linux too! :grinning:
Fixed Google Font URL to be protocol independent
Merge pull request #159 from syndbg/patch-1

Updated information about Atom availability
Merge pull request #156 from iElectric/master

note the difficulty of deployment chapter, fixes #139
Merge pull request #155 from MarkusH/lazy-fk-reference

Use lazy evaluated ForeignKey references to prevent future problems
Added regex simple example.

Simple example....
Merge branch 'master' of github.com:DjangoGirls/tutorial
Typo fixes
Merge pull request #158 from goranche/master

Deployment needs a persistent database
Merge pull request #144 from andriykohut/patch-1

Fixes for heroku-push on Windows
Use original heroku-push repo instead of fork

Fix for windows was merged https://github.com/ddollar/heroku-push/pull/11
I'll try to find time to roll-back to `git push` version + recent changes, but for now it should work
Merge pull request #161 from andriykohut/patch-3

Use original heroku-push repo instead of fork
Fixed misleading inline code (differed from block code)
Updated instructions to Python 3.4.2.
Fixed #162 -- Removed \o/

The meaning of this symbol is not explained anywhere and
could be confusing.
Use waitress instead of gunicorn to work around a bug in heroku.
Added a warning to include the trailing period at the end of startproject.