I suspect #4 is more about being able to monitor infra than my particular use case here, so I'm opening this as a separate issue given it's a bit cross-cutting in terms of concerns, not sure if it's more frontend, backend or Caddy-related. Ultimately, it would be cool to be able to add routes to an Ozone Docker composer install without having to fork the repo. This would enable me to create an e.g. /stats endpoint that users could make requests to for labeller statistics. It could also be used to do things like let Ozone installs host custom feeds more easily, for instance (one could create an entire feed of news content by outputting a custom feed of XBlock's "news media" label, for instance).
Will fully understand if this is too out-of-scope for the broader project but figured I'd ask while considering how best to architect some sort of graph bot.
Hiya!
This is a little related to #4, in that I would love to be able to publish data on my labeller, see: https://bsky.app/profile/aendra.com/post/3kseyleljl62g
I suspect #4 is more about being able to monitor infra than my particular use case here, so I'm opening this as a separate issue given it's a bit cross-cutting in terms of concerns, not sure if it's more frontend, backend or Caddy-related. Ultimately, it would be cool to be able to add routes to an Ozone Docker composer install without having to fork the repo. This would enable me to create an e.g.
/statsendpoint that users could make requests to for labeller statistics. It could also be used to do things like let Ozone installs host custom feeds more easily, for instance (one could create an entire feed of news content by outputting a custom feed of XBlock's "news media" label, for instance).Will fully understand if this is too out-of-scope for the broader project but figured I'd ask while considering how best to architect some sort of graph bot.