List of tasks before shipping #30
Description
@azizshamim per our conversation the other day, what do we need to do to get an MVP version of this ready for public use? I'll start with a list. We can expand these into issues once we settle on the work to be done. NB: my personal bias is to do as little rejiggering/refactoring as possible consistent with minimum quality/safety.
- Figure out how to test it, particularly with multiple concurrent requests (@azizshamim)
- Filter backlog of issues and assign selected ones to the MVP milestone (they're all assigned to that right now).
- Update documentation/shell script usage section/code comments
- Determine hosting strategy. Heroku? Lambda? Something else?
- Determine how to access/pay for cloudconvert. Personal account/expensed? Per user/team? Corporate account?
- Settle on where converted presos should live. Source repo? Knowledge base? Some combination? Configurable?
- Determine whether configuration should be per repository, per team, or simply a single instance
- Add some form of authentication to be verified before processing requests.
cc/ @tcbyrd