Skip to content

Latest commit

 

History

History
54 lines (45 loc) · 1.5 KB

README.md

File metadata and controls

54 lines (45 loc) · 1.5 KB

Requirements

  • Python (2.6 preferred. could probably be made to work with others)
  • postgres (8+)
  • rabbitmq
  • tahoe
  • podcast producer
  • apache for production deployment
  • mplayer (for video frame and metadata extraction)

Assumptions (how we tend to deploy):

  • code is checked out into /var/www/wardenclyffe/wardenclyffe/
  • /var/www/wardenclyffe/uploads/ exists
  • everything under /var/www/wardenclyffe is owned by user 'pusher'

How to get it running.

cd /var/www/wardenclyffe/wardenclyffe/
# initialize the database
make install
# run webserver
make runserver
# in another terminal, cd to the same directory and run
./manage.py celeryd   # starts up the celery server

That probably won't work directly, but it's worth a shot. Wardenclyffe currently expects a lot of configuration variables for the various services that it talks to. I'm not sure how well it will work without working values set for most/all of these:

SENTRY_KEY
TAHOE_BASE
TMP_DIR = '/var/tmp/wardenclyffe'
WATCH_DIRECTORY = "/var/tmp/wardenclyffe/watch_dir/"
PCP_BASE_URL
PCP_USERNAME
PCP_PASSWORD
PCP_WORKFLOW
MEDIATHREAD_BASE
MEDIATHREAD_SECRET
MEDIATHREAD_POST_URL
MEDIATHREAD_PCP_WORKFLOW
ZENCODER_API_KEY
YOUTUBE_EMAIL
YOUTUBE_PASSWORD
YOUTUBE_SOURCE
YOUTUBE_DEVELOPER_KEY
YOUTUBE_CLIENT_ID
VITAL_SECRET

Certainly those individual parts won't work, but I'm not sure if the whole thing will run at all without them at least set to dummy variables.