Skip to content
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.

configure asks for and creates uploads dir, but not downloads #850

Open
jessopb opened this issue Dec 22, 2018 · 4 comments
Open

configure asks for and creates uploads dir, but not downloads #850

jessopb opened this issue Dec 22, 2018 · 4 comments
Labels
priority: low Work should be done but can stay in the backlog for now type: bug Existing functionality is wrong or broken

Comments

@jessopb
Copy link
Member

jessopb commented Dec 22, 2018

Currently, configure relies on a default home Downloads directory to be created, but will happily create Uploads. If the target OS doesn't have a Downloads directory, the daemon is unable to download content.

@tzarebczan
Copy link
Contributor

I don't think I've ever seen the daemon fail to make the default download directory on any OS. This should still be a configurable setting through the setup cli tool.

@jessopb
Copy link
Member Author

jessopb commented Dec 22, 2018

Clement's image issues were solved by typing "mkdir Downloads". the speech cli only asks for a setting for Uploads, and creates that. So far speech has by defalut been relying on standard Downloads directory supplied by the OS (which probably isn't ideal as it mixes lbry files with whatever else is downloaded.)

@jessopb
Copy link
Member Author

jessopb commented Dec 22, 2018

It may be a good point that creating the directory for lbrynet is out of scope for speech, as opposed to just maybe knowing where it is.

@jessopb
Copy link
Member Author

jessopb commented Jan 2, 2019

It's probably best to give speech siteConfig the lbrynet root environment directory, prehaps create Uploads and Downloads there, although lbrynet should be responsible for creating those.

@alyssaoc alyssaoc added type: bug Existing functionality is wrong or broken priority: low Work should be done but can stay in the backlog for now labels Jan 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: low Work should be done but can stay in the backlog for now type: bug Existing functionality is wrong or broken
Projects
None yet
Development

No branches or pull requests

3 participants