We were planning to use Github Gists to save rocks, but I don't think this would be easy to do without authentication.
Instead we could spin up a postgresql DB on railway, and then save rocks to the DB on compile.
Type
What it would do
POST
Create a new record
PUT
Update the record
Each session would get it's own session record which would link to rocks. The only data that would be stored for individual rocks is a UUID, the sessionID, ID of rock as seen in the session, and the input. log & output would be compiled on request.
API route
/historicalRock/<date>/<id>
Date format would be DDMMYYYY
Description
Each session would get it's own session record which would link to rocks. The only data that would be stored for individual rocks is a UUID, the sessionID, ID of rock as seen in the session, and the input. log & output would be compiled on request.
API route
/historicalRock/<date>/<id>
Date format would be DDMMYYYY