Closed mre closed 1 year ago
currently I need a token in the header to see the status, right? this might be a bit tricky for a simple check by the user? what about just showing the podcast_ids an the last action of it?
what about just showing the podcast_ids an the last action of it?
We would leak all podcast ids and the API could be a public endpoint, so I'm not sure if we can/should do this. 🤔
Most likely this endpoint will be used by a status page for a single podcast, so providing the token shouldn't be a big deal.
We agreed that we will use MySQL's event scheduler to remove events older than 7 days.
Unfortunately the event
keyword is not supported by PlanetScale.
See https://planetscale.com/docs/reference/mysql-compatibility and https://github.com/planetscale/discussion/discussions/265.
can be testen locally using the stack
repo?
with the new changed in stack
it should be possible to test it there. according to https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_event_scheduler it is ON by default anyways.
timestamp
field to created
Example response:
{
"1": {
"latestUpdates": {
"metadata": "2022-12-23T15:03:47.000Z",
"detailedStreams": "2022-12-23T15:05:14.000Z",
"listeners": "2022-12-23T15:05:17.000Z",
"aggregate": "2022-12-23T15:05:12.000Z",
"followers": "2022-12-23T15:04:00.000Z",
"episodes": "2022-12-23T15:04:03.000Z",
"performance": "2022-12-23T15:05:19.000Z"
}
},
"2": {
"latestUpdates": {
"listeners": "2023-01-30T11:30:38.000Z"
}
}
}
This is a new endpoint, which returns the timestamps of the latest endpoint calls per account, e.g.
It is helpful for building an API status page in the future.