search

rmcauley / rainwave

Rainwave Site and Radio Controller
http://rainwave.cc
GNU General Public License v2.0
193 stars 38 forks source link

instructions for testing/dev do not work #74

Closed eyecreate closed 9 years ago

eyecreate commented 9 years ago

I follwed the instructions for frontend dev on a fresh ubuntu machine and got complaints about the DB. A repeatable testing env will help make running easier. A nice solution could be Vagrant.

BreadMaker commented 9 years ago

Another one to consider could be Docker.

rmcauley commented 9 years ago

Ack, sorry about that. The main problem is as soon as we make a database schema change I need to update the sample DB that's in the Git repository. I'll post a fresh version and follow the instructions from scratch as you would, and try again. (I'm booked solid the next few days, though, so it might be a bit of a wait, sorry :( )

williamjacksn commented 9 years ago

I have a Vagrantfile that I use for this personally. I can make sure it is still in working order and commit it if there is interest.

BreadMaker commented 9 years ago

:+1: to that, @williamjacksn

rmcauley commented 9 years ago

Keep in mind that the Vagrant file will require you (I think) to have a Postgres server at the ready, and will use your own collection of MP3s. This is different from the easy/sample startup, which if I was more diligent in keeping up to date, wouldn't require either. :/

williamjacksn commented 9 years ago

The Vagrantfile will set up the Postgres server in the virtual machine. You do need your own mp3 files, though. See https://github.com/rmcauley/rainwave/blob/master/etc/README_DEV.md

williamjacksn commented 9 years ago

Also I wrote the Vagrantfile with an eye to back-end and API development, not front-end development. So it needs some work.

rmcauley commented 9 years ago

I've reconstructed the sample DB file and tested it locally, it ought to work now if anyone wants to just develop against the front-end. Keep in mind not all functions may work, specifically the more DB-intensive functions such as requesting favourites or requested unrated songs.

If anyone ever needs to reconstruct the sample, it's quite easy. Take the rainwave_dev.conf, rename it "[your username].conf" and edit it to point at your own music files, delete etc/sample.sqlite, python db_init.py && python rw_scanner.py, python rw_api.py ought to do the trick. Any issues try rw_backend.py instead and in a separate shell run rw_get_next.py, then restart rw_api.