`Who` can/should use our image uploading + resizing service?
- Dominant language
- Elixir
- Stars
- 108
- Forks
- 20
- Avg merge
- 21h 46m
- Merged PRs (30d)
- 4
Description
The "demo" version of the `imgup` App will be open to allow people to test it.
We will not `DELETE` the files unless the `AWS S3` bill gets out of hand e.g: bots start uploading.
I don't expect nefarious people to discover/use the `imgup` App ...
but if they do we will rapidly respond and put _all_ uploading behind `Auth`.
The `REST API` will have `Auth` ASAP because that is where abuse is most likely to originate.
See:
But we need to enable `logging`: https://github.com/dwyl/logs/issues/1
so that we can:
A. See `who` is trying the demo and from _where_.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the demo App and REST API context described in the issue, along with the linked dwyl/logs issue. Determine how logging can identify who is using the demo and from where, while considering the AWS S3 upload path. Done means the required logging behavior and its scope are clearly implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, elixir
- Domain
- api, backend, cloud, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100