Skip to content

Commit

Permalink
fixup - tweak wording
Browse files Browse the repository at this point in the history
  • Loading branch information
ploxiln committed Feb 8, 2019
1 parent 3e8b8eb commit 99594f5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/config-database-setup.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ To set up a new database and create the initial schema, run:
PYTHONPATH=$GRAPHITE_ROOT/webapp django-admin.py migrate --settings=graphite.settings
.. note ::
In Graphite-Web 1.0 and earlier, if using Django 1.9 or later, the ``--run-syncdb`` option is needed for migrate to create tables for models without migrations (and Django 1.8 or earlier did not have this option but always exhibited this behavior). In Graphite-Web 1.1 and later all models have migrations, so ``--run-syncdb`` is no longer needed. If upgrading a database created by Graphite-Web 1.0 or earlier, you need to use the ``--fake-initial`` option for migrate: it considers an initial migration to already be applied if the tables it creates already exist.
Graphite-Web 1.0 and earlier had some models without migrations, and with Django 1.9 or later, the ``--run-syncdb`` option was needed for migrate to create tables for these models. (Django 1.8 or earlier did not have this option, but always exhibited this behavior.) In Graphite-Web 1.1 and later all models have migrations, so ``--run-syncdb`` is no longer needed. If upgrading a database created by Graphite-Web 1.0 or earlier, you need to use the ``--fake-initial`` option for migrate: it considers an initial migration to already be applied if the tables it creates already exist.
If you are experiencing problems, uncomment the following line in /opt/graphite/webapp/graphite/local_settings.py:

Expand Down

0 comments on commit 99594f5

Please sign in to comment.