FlowFuse / FlowFuse/usage-ping-collector
Migrate Storage to FlowFuse
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 1
Description
### Description
Given that we now have FlowFuse Tables, there is no reason for us to be using custom hosted postgres for this. We should migrate the existing data into FlowFuse Tables, and then update the relevant Dashboards and Reports to point to the new storage layer.
### Epic/Story
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the current custom hosted PostgreSQL storage integration and the queries used by the Dashboards and Reports. Migrate the existing data into FlowFuse Tables, update those consumers to use the new storage layer, and verify that the data remains available through the Dashboards and Reports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql
- Domain
- analytics, backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100