🚧 Project Direction: Moving from AWS-dependent to Local-first Problem #3
Closed
MUBENDIRAN
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Cloud Insight AI depends on AWS services (S3, ECS, Comprehend), which are no longer active due to free tier limits.
This makes the project:
Not runnable for contributors
Hard to test locally
Less practical for real collaboration
Proposed Direction
Shift to a local-first architecture:
Replace:
S3 → Local JSON / SQLite storage
ECS → Local Docker execution
Comprehend → Optional NLP (local or pluggable)
Goal
Anyone should be able to:
git clone ...
docker run ...
and see the system working instantly.
Open Questions
Should we use SQLite or keep JSON-based storage?
Should NLP be optional or removed entirely?
Do we keep AWS as an optional plugin?
Call for Contributors
Looking for help with:
Refactoring storage layer
Removing AWS dependencies
Improving local execution
Beta Was this translation helpful? Give feedback.
All reactions