Cluvio is generally used with databases running on servers, whether on cloud providers (AWS, Azure, Google Cloud, ...) or within your own server infrastructure. This means that the database (or the SSH tunnel server, when used) needs to be reachable via a DNS hostname or an IP address, that is accessible from "the internet".
This requirement makes it hard to try out Cluvio with a database running on your own laptop or PC, esp. when it is behind a NAT translating router (which is by far the most common setup for a company or home network).
There are few approaches that can be used to work around this limitation, and although we would not recommend these for production use, they can be used for testing:
- If your internet connection has a statically assigned IP address, or you use a service like DynDns, you could set up port forwarding from your router to a port running on a local PC or laptop. In Cluvio, you would use the router IP address as Host, the port that the router is set up to forward as Port, and the remaining settings as usual for your database.
- Use a service like ngrok to set up a tunnel between your locally running database. You would use the `ngrok tcp` command and in Cluvio use the ngrok command output as host and port while using the rest of the settings as usual for your database. Please make sure that you use SSL encryption for the database connection in Cluvio (check the "Require SSL" checkbox), in case you use the 3rd party tunnel service with sensitive data.
- Spin up a small test database on one of the cloud providers (AWS RDS, Azure, Google Cloud) and restore a dump of your database there. This can be done quickly and can be very cheap, mitigating some of the downsides or complexity of the previous 2 approaches.