109
edits
Raindrop/Milestone Planning: Difference between revisions
→Hosted Goal
| Line 99: | Line 99: | ||
* Will merge 'run-raindrop' with the API; there is no need to have 2 distinct processes for this, so long as we can differentiate between 'async' requests (eg, 'start synching') versus 'sync' request (eg, API calls) | * Will merge 'run-raindrop' with the API; there is no need to have 2 distinct processes for this, so long as we can differentiate between 'async' requests (eg, 'start synching') versus 'sync' request (eg, API calls) | ||
* Developers will need solutions to allow them to test code without requiring a full deployment and without checking in code; must continue to be able to test locally *before* checking in. | * Developers will need solutions to allow them to test code without requiring a full deployment and without checking in code; must continue to be able to test locally *before* checking in. | ||
=== API Keys === | |||
We should not store API keys for APIs that Raindrop consumes in the public source repo. | |||
* Figure out where to store API keys for hosted version. | |||
* Work out a process for a developer to get new API keys. At the very least document on the wiki what to do, and add to it for every new API. Ideally have a web app that could help the developer get the API key and inject it into Raindrop. | |||
* Make changes to raindrop to pull in these API keys or a web UI to allow input of the API keys. | |||
=== Logging === | === Logging === | ||