Frequently Asked Questions

How do you connect to a local database when running Tonic in a docker container locally?

If the locally running db you wish to connect to is itself running in a docker container then please run: docker inspect and find the Gateway IP address in the "networks" section. Use this IP address as the server address in Tonic.
If the locally running db is NOT running in a container but is just running on the machine then you can use the address: host.docker.internal if you are running on Windows or Mac. If on linux you can use which will be the IP address of the docker0 interface.

I whitelist access to my database, what are your static IPs?

How do I check my current version of Tonic or get my current workspaceId?

Click on the Tonic logo in the upper left corner:

How does Tonic interact with our source database? Does it need to write anything to it?

Tonic will never write to the source database. In fact, we strongly encourage you to connect with a database user with non-write permissions.
When running the Tonic UI, Tonic issues queries to grab upwards of 100 records per table. These records are then made available to view through the UI. When running a Tonic job, Tonic starts by generating a schema dump of the source database. Tonic will proceed to then grab data from each table sequentially (this can be optionally configured to support parallelism).

Should I be using a read replica as the source database?

Read replica databases impose restrictions on how long a query can run before it times out. Tonic highly encourages the use of a restored snapshot instead to avoid query timeouts.
Last modified 3mo ago