Problem
We currently fetch ALL conversation records when we hit the ChatApi.Conversations.list_conversations_by_account/2 method (i.e. we set no limit or offset in our query, nor do we have cursors or anything like that)

This will not scale very well as more and more data gets added.

Solution
To start off, let's do the following:

• Implement another version of `ChatApi.Conve

Hi,

It'd love to try out alloy_ci . We run almost everything in kubernetes (incl. gitlab runner) and I think it would be awesome if there was a template / manifests to deploy alloy on kubernetes.
This would make trying it out for evaluation purposes much easier.
Have no strong opinions on how a k8s example templates should be packaged but these are some options that come to my mind:

• simpl

Found through review of dwyl/phoenix-ecto-append-only-log-example#11

Link currently points to https://github.com/dwyl/phoenix-ecto-append-only-log-example/pull/2/files#diff-db55bfd345510f8bbb29d36daadf7061R21, which at the time was part of a PR.

Should we now update this to https://github.com/dwyl/phoenix-ecto-append-only-log-example/blob/3eb130e103cef05ef57e5d1fcd2