In b049114 we enabled support for remote databases, and added a number of sanity checks to make sure that (a.) the user passes good options either via a config file or via parameters, and (b.) a valid connection was indeed established after the Neo4j bolt driver is created.
However, we currently cannot use neo4j.comptox.ai as a hostname. Tests using either the neo4j:// or bolt:// protocols failed to provide a good result. It is currently unclear whether this is a local issue (e.g., it can be fixed by tweaking comptox_ai.db.GraphDB._connect()) or if it is something that will require tweaking on the side of the ComptoxAI server (e.g., a DNS issue, NGINX configuration, etc.).
In b049114 we enabled support for remote databases, and added a number of sanity checks to make sure that (a.) the user passes good options either via a config file or via parameters, and (b.) a valid connection was indeed established after the Neo4j bolt driver is created.
However, we currently cannot use neo4j.comptox.ai as a hostname. Tests using either the neo4j:// or bolt:// protocols failed to provide a good result. It is currently unclear whether this is a local issue (e.g., it can be fixed by tweaking
comptox_ai.db.GraphDB._connect()
) or if it is something that will require tweaking on the side of the ComptoxAI server (e.g., a DNS issue, NGINX configuration, etc.).