Hi! I’m trying to create some kind of ‘customer object’ (which will be managed from another server/web ui). This object should contain data like their current plan (for example 100k emails per month quota) and verified domain names which the customer is allowed to send emails from. Where would you store (and fetch) this kind of data? Or would you perhaps recommend another way of achieving something like this?
Hey there @astounding-quail, thanks for posting. To ensure the fastest resolution to your issue, please review the following and follow all the steps:
At the moment our external data source support includes SQLite and Redis. I’d say SQLite is more appropriate.
Thanks @yearning-hyena ! One more question – would you then run the database on the MTA side, or on the ‘web ui’ side?
With SQLite it would run on the MTA. You could look at setting up syncing so that the webUI copy of the database is synced to the mTA.
Aah, sounds good. Thanks!
I have found this: https://github.com/rqlite/rqlite. Maybe it’s useful.
sqlite support is built in to kumo: open - KumoMTA Docs
If you plan to have multiple nodes, then coordinating updating sqlite database on each of them can be challenging.
It may just be simpler to deploy eg: a json file that has your data inside it, together with kumo.json_load and kumo.memoize to load and cache the data