search

xdarklight / cm-update-server

This provides the server-side API for letting a user download ROMs through the CMUpdater app. In other words: this is an open source clone of the get.cm API implemented with NodeJS.
MIT License
10 stars 9 forks source link

Resource not Found #5

Closed thenameisnigel-old closed 8 years ago

thenameisnigel-old commented 8 years ago

This may be a n00b-ish question, but when I'm running the server, where exactly does the ROM files go? I attempted to put them in ./data/subdirectory, ./website/build/subdirectory, and even in the root of the directory and I always get a resource not found error message. @xdarklight

thenameisnigel-old commented 8 years ago

Ah, figured it out, thanks!

thenameisnigel-old commented 8 years ago

Wait, no I didn't.

xdarklight commented 8 years ago

I haven't tried to deliver the ROM files through cm-updater yet. My setups always included a reverse-proxy in front of cm-update-server which takes care of serving the download files (because in my case it's not only one server but a small "CDN" which delivers the ROM files).

Nevertheless, I'll look into this later this week - I'm sure that it has to be possible.

xdarklight commented 8 years ago

I have pushed a comment in config/default.js: mkdir -p ./data/files/downloads/ Put all zip files in there, then you'll be able to reach them through localhost:3000/downloads/nameofyour.zip

thenameisnigel-old commented 8 years ago

Thank you! @xdarklight