Permalink
Browse files

Fix #568 -- document django-admin.py instead of now inexistent manage.py

  • Loading branch information...
1 parent 15a2539 commit e94d5615c8ed764cf6d2c1f6c3c1f8dc3be46377 @brutasse brutasse committed Jan 14, 2014
View
@@ -43,8 +43,7 @@ you are doing.
Once you have installed graphite you must initialize its database like so:
export PYTHONPATH=$PYTHONPATH:$GRAPHITE_ROOT/webapp
-cd $GRAPHITE_ROOT/webapp/graphite/
-sudo python manage.py syncdb
+django-admin.py syncdb --settings=graphite.settings
Note that if you wish to use a custom database setup (like MySQL or Postgres)
you will need to make those configuration changes first. See the "Custom
@@ -130,8 +129,7 @@ Edit the $GRAPHITE_ROOT/webapp/graphite/local_settings.py
In particular you will need to uncomment and modify the ``DATABASES`` setting.
Once you have done this, we need to tell Django to create our tables.
-cd $GRAPHITE_ROOT/webapp/graphite/
-sudo python manage.py syncdb
+PYTHONPATH=$GRAPHITE_ROOT/webapp django-admin.py syncdb --settings=graphite.settings
# you will be prompted to create an admin user, this is a good idea
Restart apache and you should see the graphite webapp on the main page.
@@ -22,7 +22,7 @@ if [ ! -f /etc/httpd/conf.d/graphite.conf ]; then
cp ${GRAPHITE_PATH}/examples/example-graphite-vhost.conf /etc/httpd/conf.d/graphite.conf
fi
-python ${GRAPHITE_PATH}/webapp/graphite/manage.py syncdb --noinput
+PYTHONPATH=${GRAPHITE_PATH}/webapp/ django-admin.py syncdb --noinput --settings=graphite.settings
chown -R apache.apache ${GRAPHITE_PATH}/storage
chown -R apache.apache ${GRAPHITE_PATH}/webapp
@@ -275,8 +275,9 @@ See the
for full documentation of the DATABASE setting.
.. note ::
- Remember, setting up a new database requires running ``manage.py syncdb`` to create the initial
- schema
+ Remember, setting up a new database requires running
+ ``PYTHONPATH=$GRAPHITE_ROOT/webapp django-admin.py syncdb --settings=graphite.settings``
+ to create the initial schema.
Cluster Configuration
---------------------
@@ -28,8 +28,10 @@ Carbon may be run within Virtualenv by `activating virtualenv`_ before Carbon is
Running Graphite-web Within Virtualenv
--------------------------------------
-Running Django's manage.py within virtualenv requires `activating virtualenv`_ before executing
-as normal.
+Running Django's ``django-admin.py`` within a virtualenv requires using the
+full path of the virtualenv::
+
+ /path/to/env/bin/django-admin.py <command> --settings=graphite.settings
The method of running Graphite-web within Virtualenv depends on the WSGI server used:
View
@@ -95,7 +95,7 @@ Carbon and Graphite-web are installed in ``/opt/graphite/`` with the following l
- ``graphite/``
- Location of ``manage.py`` and ``local_settings.py``
+ Location of ``local_settings.py``
- ``content/``
@@ -164,7 +164,7 @@
# Django models such as saved graphs, dashboards, user preferences, etc.
# Metric data is not stored here.
#
-# DO NOT FORGET TO RUN 'manage.py syncdb' AFTER SETTING UP A NEW DATABASE
+# DO NOT FORGET TO RUN 'django-admin.py syncdb' AFTER SETTING UP A NEW DATABASE
#
# The following built-in database engines are available:
# django.db.backends.postgresql_psycopg2

0 comments on commit e94d561

Please sign in to comment.