GAE/Cloud Run are certainly possibilities, I'll have to look into them.
> I'd suggest porting to key/value pair DBs like mongo or firestore.
Why? The data set feels pretty "relational" to me (contests have divisions, divisions have scorings and results, results have players, players have sponsors) and seems to fit SQL. To be fair though, I've not used Mongo or Firestore or a NoSQL db in general before.
The "scorings" part is the only thing that tripped me up designing a schema since it varies between divisions in a contest as well as between contests themselves, so I ended up w/ a JSONB column for scoring rubric for divisions and then in the results table there's both final_score and scoring_breakdown columns, the beakdown being another JSONB column w/ the individual category results.
Interesting, I hadn't heard of Dokku before (looks similar to Flynn and Deis (looked into those back in 2016 before k8s was the de facto choice) but still actively developed) and I overlooked Lightsail. I'll have to price out DigitalOcean as well, I used them for a project in school because they gave out free credits and the experience was good iirc.
Read it as "cost-efficiently externally hosting" then I guess. For a PoC I might host locally just to show it off to others, but I wouldn't want to deploy it there long-term, mostly since I'm not physically near said lab for several months at a time so if things went down it'd be a drag.
Can’t you take photos in RAW though, on iPhones at least? My assumption is that would produce a file w/o the AI processing applied that you could then process yourself, but I don’t know for sure if that’s the case.
the exact thinkpad style is probably patented but it's a pointing stick, a feature common across laptops in the past. I know for sure that some Dells (TrackStick) and HPs (PointStick) had them.
For video theres VapourSynth[0], not sure of an equivalent for audio outside of just scripting ffmpeg but that’s probably not as flexible as what you’re after.
> I'd suggest porting to key/value pair DBs like mongo or firestore.
Why? The data set feels pretty "relational" to me (contests have divisions, divisions have scorings and results, results have players, players have sponsors) and seems to fit SQL. To be fair though, I've not used Mongo or Firestore or a NoSQL db in general before.
The "scorings" part is the only thing that tripped me up designing a schema since it varies between divisions in a contest as well as between contests themselves, so I ended up w/ a JSONB column for scoring rubric for divisions and then in the results table there's both final_score and scoring_breakdown columns, the beakdown being another JSONB column w/ the individual category results.