This message was deleted.
# general
b
This message was deleted.
c
Hi Adam, I haven’t heard of anyone trying to self host in a SQLite db. We used to use mongo but switched to postgres since that seemed to be more generally acceptable for self hosting.
If I can ask, what’s the main thing sqlite would do for you? I hear you 100% that infracost problems shouldn’t block CI ever. We’ve raised this issue to try and get some ideas on the best way to handle that.
n
I think there are two layers: how to ensure ci downtime doesn't happen due to infracost unavailability, and how useful should the local infracost binary be when infracost is unavailable
I'd personally rather have stale prices than no prices
One benefit of SQLite is that you don't even need to download the entire database to query it
And could possibly fit the entire thing, SQLite price list + API + binary to use it in a single docker image
c
Ok, yeah that’s interesting.
Yeah I’d say see if anybody else chimes in on slack, but maybe also great a GH issue to see how much interest there is.
n
Should this be in the cli repo? Or the API one?
c
I think cli repo because that has the most visibilty
n
Where can I learn more about the current snapshots?
c
Hmm what kind of info are you looking for?
n
Like how they are generated, how they are loaded
What their schema is
c
I don’t think we have specific docs for that but you can look at the cmd directory in the cloud_price_api repo. The basic steps are
db:setup
(that creates the tables so should lead you to the schema), then
data:scrape
which queries the cloud provider apis and populates the data.
n
@crooked-daybreak-55253 thanks for the pointers, I think I've figured this out