ports/181042: [patch] www/py-graphite-web: Correct setup directions and dependency on mod_wsgi
Brad Davis
brd at FreeBSD.org
Mon Aug 5 03:20:00 UTC 2013
>Number: 181042
>Category: ports
>Synopsis: [patch] www/py-graphite-web: Correct setup directions and dependency on mod_wsgi
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Mon Aug 05 03:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Brad Davis
>Release: FreeBSD 9.1-RELEASE-p5 i386
>Organization:
>Environment:
>Description:
Add a dependency on mod_wsgi since graphite is not useful without it
Refine the directions on setting graphite up
>How-To-Repeat:
>Fix:
--- py-graphite.patch begins here ---
Index: www/py-graphite-web/Makefile
===================================================================
--- www/py-graphite-web/Makefile (revision 324246)
+++ www/py-graphite-web/Makefile (working copy)
@@ -15,7 +15,8 @@
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}cairo>=1.8.10:${PORTSDIR}/graphics/py-cairo \
${PYTHON_PKGNAMEPREFIX}carbon>=${PORTVERSION}:${PORTSDIR}/databases/py-carbon \
${PYTHON_PKGNAMEPREFIX}django>=1.3.1:${PORTSDIR}/www/py-django \
- ${PYTHON_PKGNAMEPREFIX}django-tagging>=0.3.1:${PORTSDIR}/www/py-django-tagging
+ ${PYTHON_PKGNAMEPREFIX}django-tagging>=0.3.1:${PORTSDIR}/www/py-django-tagging \
+ ${APACHE_PKGNAMEPREFIX}mod_wsg>0:${PORTSDIR}/www/mod_wsgi3
FETCH_ARGS= -pRr
USE_PYTHON= -2.7
Index: www/py-graphite-web/pkg-message
===================================================================
--- www/py-graphite-web/pkg-message (revision 324246)
+++ www/py-graphite-web/pkg-message (working copy)
@@ -5,14 +5,14 @@
To run graphite, you will need to setup Apache by creating a vhost similar to
the following:
+# I've found that an equal number of processes & threads tends
+# to show the best performance for Graphite (ymmv).
+WSGIDaemonProcess graphite processes=5 threads=5 display-name='%{GROUP}' inactivity-timeout=120
WSGIImportScript /usr/local/etc/graphite/graphite.wsgi process-group=graphite application-group=%{GLOBAL}
<VirtualHost *:80>
ServerName graphite
DocumentRoot "/usr/local/graphite/webapp"
- # I've found that an equal number of processes & threads tends
- # to show the best performance for Graphite (ymmv).
- WSGIDaemonProcess graphite processes=5 threads=5 display-name='%{GROUP}' inactivity-timeout=120
WSGIProcessGroup graphite
WSGIApplicationGroup %{GLOBAL}
@@ -43,7 +43,11 @@
</Directory>
</VirtualHost>
+Configure the SECRET_KEY setting in: ${PYTHON_SITELIBDIR}/graphite/app_settings.py
+Copy the ${PYTHON_SITELIBDIR}/graphite/local_settings.py.example to
+${PYTHON_SITELIBDIR}/graphite/local_settings.py
+
Then initialize the sqllite user database and create the admin user:
python ${PYTHON_SITELIBDIR}/graphite/manage.py syncdb
--- py-graphite.patch ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list