Corrections to readme

README.md

@@ -17,7 +17,7 @@ mobile app (some day). **Feature [suggestions](https://ant.sr/contact) are welco
 
 ## Setup for Development
 - Install system-wide dependencies  
-    `sudo apt-get install python python-pip python-virtualenv libxml2-dev libxsl-dev`
+    `sudo apt-get install python python-pip python-virtualenv redis-server libpq-dev libxml2-dev libxslt1-dev`
 - Create and/or activate your virtualenv    
     Create: `virtualenv venv`
     Activate: `. venv/bin/activate`
@@ -39,18 +39,17 @@ mobile app (some day). **Feature [suggestions](https://ant.sr/contact) are welco
 You should now be able to access the instance on port 5000.
 
 ## Production
-To run BusMap in production you need an application server. I use uWSGI in emperor mode. On Debian, this means that per-application uWSGI configs belong in `/etc/uwsgi/apps-enabled/appname.ini`
+To run BusMap in production you need an application server. I use uWSGI. On Debian, this means that uWSGI configs belong in `/etc/uwsgi/apps-enabled/appname.ini`
 Here's a sample uWSGI config for this application:
 
     [uwsgi]
-    plugins = python
-    module = app
-    callable = app
+    plugins = python34
+    module = app:app
 
     # Paths
     base = /var/www/pybusmap
     home = %(base)/venv
-    chdir = /var/www/pybusmap
+    chdir = %(base)
     pythonpath = %(base)
     socket = %(base)/uwsgi.sock
 
@@ -59,9 +58,8 @@ Here's a sample uWSGI config for this application:
     gid = www-data
 
     # Worker behavior
-    die-on-term = true
     vacuum = true
-    smart-attach-daemon = /tmp/pybusmap-celery.pid %(home)/bin/celery -A celerytasks.celery worker --beat --pidfile=/tmp/pybusmap-celery.pid --logfile=%(base)/log/celery/%n.log
+    attach-daemon = %(home)/bin/celery -A celerytasks.celery worker -B --logfile=%(base)/log/celery/beat-%n.log
 
 ## License
 PyBusMap is MIT-licensed. Please use/fork/share it. Contributions are welcome.
\ No newline at end of file