Hi.
I am consulting with a small non-profit that would like to run the open-source version of CartoDB on their own (cloud) infrastructure. Because they would potentially like to run it at scale (or at least know it won't catastrophically tip over under variable load), I'm attempting to run it as a collection of services rather than an impossible to scale single-host install.
Unfortunately I am repeatedly running into severe configuration and dependency problems that impact core features of the software, and trying to troubleshoot them without good ops documentation is very frustrating.
So, my questions:
- Does anyone know of any definitive operations info for running open-source CartoDB on more than one host?
- Are there any organizations or individuals out there who are successfully running it, and who might be available to connect or consult?
For what it's worth, I have a 'working' multi-container Docker solution. I put working in quotes because while it runs and performs some basic tasks, there are features failing due to (it appears to me) inter-service (or even intra-service? who knows?) communication failures. There are clearly some vital architecture details I'm missing.
For instance, specifics of how the invalidation service is supposed to function do not appear anywhere I've looked, and it appears to be an important part of the overall application, being relied on by multiple other components. From the example CartoDB app configurations, that service claims to be available on port 3142, which is a non-standard port for almost everything. Additionally, parts of the codebase refer to invalidating the varnish cache, but the client object (obtained in the PlPython Postgres functions for dealing with "ghost tables") which hits the invalidation service endpoint is a Redis client. And, to make it more confusing, in at least one Carto company slide deck I saw the invalidation service referred to as a Node app, for which I've been able to find no source code at all.
I need someone who can confirm this thing can actually be run by
anyone other than Carto. I'm extremely close to telling my client that the software simply isn't usable, and that they need to begin evaluating other geoservers.
Information sources I've looked at so far:
If anyone has any leads on someone (anyone!) able to explain how to successfully operate open-source CartoDB, I would very much appreciate them.
Thanks,
Nick