You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker-compose example (as of now) does not include any volumes for nodeodm, and the docs (on nodeodm) mention /mnt/external_hd:/var/www/data but do not mention about /var/www/tmp which also has a tendency to
We could add a --node-dir flag similarly to --media-dir and --db-dir that allows users to specify a location for mounting those two directories. I'd welcome a PR for that, noting that there might be some issues making it work with the --default-nodes flag when that flag is set to > 1.
What's your browser and operating system?
Chrome 79 on macOS (High Sierra)
What is the problem?
docker-compose example (as of now) does not include any volumes for nodeodm, and the docs (on nodeodm) mention
/mnt/external_hd:/var/www/data
but do not mention about /var/www/tmp which also has a tendency toWhat should be the expected behavior?
I suggest:
How can we reproduce this?
Its a docs and example file issue - you can have a look at the in line links above to see what i refer to.
The text was updated successfully, but these errors were encountered: