Create IAC
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 3
Description
The code should run on GCP. To decide specific tool. Frontend and backend should run in separate containers. They should use scaling in when idle (remember to add proper cooldown period to avoid terminating running knowledge ingestion tasks - a known issue described in decision log). Use supabase as database system.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the decision log entry describing the known cooldown issue, then inventory the existing frontend, backend, and knowledge-ingestion entry points before choosing GCP tooling. Done means the application runs in separate frontend and backend containers on GCP, uses Supabase, and scales down safely without terminating active ingestion tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, python, supabase
- Domain
- backend, cloud, databases, devops, frontend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100