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.

Sign up for GitHub

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

Jump to bottom

Feat: Store Metadata and Image Classification/Info #3

Closed
6 tasks done
nelsonic opened this issue Nov 8, 2023 · 3 comments · Fixed by #28
Closed
6 tasks done

Feat: Store Metadata and Image Classification/Info #3

nelsonic opened this issue Nov 8, 2023 · 3 comments · Fixed by #28
Assignees
@LuchoTurtle
Labels
discuss Share your constructive thoughts on how to make progress with this issue documentation Improvements or additions to documentation elixir Pull requests that update Elixir code enhancement New feature or enhancement of existing functionality feedback Feedback from people using the App or any other repo priority-1 Highest priority issue. This is costing us money every minute that passes. T4h Time Estimate 4 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@nelsonic
Copy link
Member

nelsonic commented Nov 8, 2023 •
edited by LuchoTurtle
Loading

As discussed on standup this morning, the app you have built in #2 doesn't currently store any data.
This is ok for a basic demo but we want to take this a bit further.

Please let me know when you have a few mins to discuss a potential schema for the data we can store.

I'm thinking the minimum should be:

  • url - the image that was uploaded (preferably to b2 but S3 for now ideally using the imgup API...)
  • height - the height in pixels of the image
  • width - the width in pixels of the image
  • info - the String describing the image
  • person_id - optional for now. but eventually required if there is too much spam.

For analytics (and spam prevention) purposes, we should also have an agent table similar to Hits where User Agent (Browser/Device) is stored: /lib/hits/useragent.ex#L6-L8

  • What else?
@nelsonic nelsonic added enhancement New feature or enhancement of existing functionality elixir Pull requests that update Elixir code priority-1 Highest priority issue. This is costing us money every minute that passes. T4h Time Estimate 4 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies labels Nov 8, 2023
@nelsonic nelsonic mentioned this issue Nov 8, 2023
Closed
5 tasks
@nelsonic nelsonic added documentation Improvements or additions to documentation feedback Feedback from people using the App or any other repo discuss Share your constructive thoughts on how to make progress with this issue labels Nov 8, 2023
This was referenced Nov 8, 2023
Merged
Closed
@nelsonic
Copy link
Member Author

As noted by @ndrean in #18 an SQLite DB is a good idea for this project given that the machine already has an attached Volume. 💭 Please time-box exploring this to T2h and if it's too much effort, use a Postgres instance with auto-shutdown.

@nelsonic nelsonic mentioned this issue Nov 21, 2023
Open
15 tasks
@nelsonic nelsonic pinned this issue Nov 21, 2023
@LuchoTurtle
Copy link
Member

I'll start once I'm finished refactoring the models managing system and it's deployed to fly.io.

@nelsonic
Copy link
Member Author

Sweet! 🍭
Looking forward to it. LMK if/how I can help. 👌

@LuchoTurtle LuchoTurtle mentioned this issue Dec 4, 2023
Merged
@LuchoTurtle LuchoTurtle unpinned this issue Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LuchoTurtle LuchoTurtle

Labels
discuss Share your constructive thoughts on how to make progress with this issue documentation Improvements or additions to documentation elixir Pull requests that update Elixir code enhancement New feature or enhancement of existing functionality feedback Feedback from people using the App or any other repo priority-1 Highest priority issue. This is costing us money every minute that passes. T4h Time Estimate 4 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
dwyl app kanban
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[PR] Setting up Postgres and adding upload to S3 dwyl/image-classifier
2 participants
@nelsonic @LuchoTurtle