One longstanding issue is the fact that the logs are not uploaded to any centralized store. This is especially a problem because it makes observability from any location difficult.

Luckily, the logging solution being used throughout the repo, pino, has transports support, meaning more destinations can be added for log output. The planned destination is Parseable.

Parseable seems to be a good solution based on my use-case, which is just being able to see the logs and not doing any transformation or visualization with them (so no need for elasticsearch/kibana). The main issue is that there is no transport library for Parseable yet, so that will need to be done first. The instance itself will likely be hosted on Railway, however there is room for self-hosting if that becomes a need later on.

Currently, an action exists for the web client only. The other services (updater, bot) should also have actions to automate the building of their respective docker images.

Updates currently happen every 20 minutes, starting from when the updater was started. It would be nice to update with a cron-like interval instead, to give more predictability about when updates occur.