We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
maybe we should put those tokens in db instead.
The text was updated successfully, but these errors were encountered:
I think it should be fine, at worst we can just change it.
Besides db, other options environment variable, config file.
Summary of API tokens: For Mendeley: server/shareread/document/metadata.py For DropBox: we are using certificate so no worries?
Sorry, something went wrong.
Yep. It's fine. I just worry about security issues in the future. For now, let's focus on the features.
On Wed, Jun 22, 2016 at 10:36 PM Blie Arkansol [email protected] wrote:
I think it should be fine, at worst we can just change it. Besides db, other options environment variable, config file. Summary of API tokens: For Mendeley: server/shareread/document/metadata.py For DropBox: we are using certificate so no worries? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub #5 (comment), or mute the thread https://github.com/notifications/unsubscribe/ACFQQP4tjb70YgqydTatOV__Z4IoQYZxks5qOhtcgaJpZM4I8JRj .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub #5 (comment), or mute the thread https://github.com/notifications/unsubscribe/ACFQQP4tjb70YgqydTatOV__Z4IoQYZxks5qOhtcgaJpZM4I8JRj .
No branches or pull requests
maybe we should put those tokens in db instead.
The text was updated successfully, but these errors were encountered: