internalfx / thinker

A command line tool to ease development and administration.
ISC License
234 stars 14 forks source link

Colon in URL string #6

Open ghost opened 8 years ago

ghost commented 8 years ago

Thinker works great for cloning a DB from localhost to a remote host. However, I had the need to switch to a different PaaS (Compose) and their connection string starts with an x followed by a colon

x:YXYZ.....

that makes thinker think after the color follows the port number.

Can you think of any solution to that?

internalfx commented 8 years ago

I'm not familiar with how compose works.

At the risk of asking a dumb question...Why does it start with an x:?

internalfx commented 8 years ago

I don't see any mention of the x: in their connection docs...

https://help.compose.io/docs/connecting-to-rethinkdb

ghost commented 8 years ago

At the risk of asking a dumb question...Why does it start with an x:?

To be honest I have no idea. The connection string they provide for the deployment in the account console starts with x: . I have opened a ticket at their support since I can't connect to the deployment from NodeJS server either.

I will post here if I get back from them.

ghost commented 8 years ago

Well, that's is a weird documentation in the Compose deployment overview, however, they say that x: can be ignored.

Connections to Compose require SSL that's why I couldn't connect using Thinker. In the RethinkDB connection configuration there must be the public SSL key such as "ssl": { "ca": "cert" }

BTW, the public SSL key can be transformed to a string

internalfx commented 8 years ago

So we just need a command line option for it?

like thinker clone --cert "something-goes-here"

internalfx commented 8 years ago

or perhaps thinker clone --cert someFileName

ghost commented 8 years ago

That would be great. I think in the context of thinker thinker clone --cert someFileName would be the right way to go.

sagivf commented 8 years ago

This would be very useful 👍