Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[issue] No default config created #59

Closed
sullo opened this issue Feb 23, 2022 · 0 comments · Fixed by #90 or #163
Closed

[issue] No default config created #59

sullo opened this issue Feb 23, 2022 · 0 comments · Fixed by #90 or #163
Assignees
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@sullo
Copy link
Contributor

sullo commented Feb 23, 2022

Describe the bug
According to the documentation:

The default provider config file should be located at $HOME/.config/cloudlist/provider-config.yaml and has the following contents as an example. 

However, the file is not created when installing via git.

Cloudlist version
Built from github: [INF] Current Version: 1.0.0

Expected Behavior
If installation method can't create a default config, provide one in the source tree to copy, or create one, during first run.

Screenshot of the error or bug

╰─$ ll $HOME/.config/cloudlist/provider-config.yaml
ls: /Users/sullo/.config/cloudlist/provider-config.yaml: No such file or directory
@ehsandeep ehsandeep added Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. labels Mar 10, 2022
@LuitelSamikshya LuitelSamikshya self-assigned this Mar 18, 2022
@LuitelSamikshya LuitelSamikshya linked a pull request Mar 22, 2022 that will close this issue
@LuitelSamikshya LuitelSamikshya added the Status: Review Needed The issue has a PR attached to it which needs to be reviewed label Mar 23, 2022
@ehsandeep ehsandeep added Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Status: Review Needed The issue has a PR attached to it which needs to be reviewed labels Mar 23, 2022
@ehsandeep ehsandeep linked a pull request Jun 9, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants