Ionic Pro: SSH Key Best Practice

Sorry if this is a duplicate topic, but I’m a bit unsure how to set up multiple dev boxes up with the new ionic pro environment. We have two users (developers) on pcs along with a “shared” mac. We have a local git server as our origin, and I’m wondering if we should set up separate ssh keys for each box to connect to ionic in order to push updates. Furthermore, should we only really be pushing updates to ionic from one box, and one master branch? I was using the windows box to push updates, but now that we’ve branched out to iOS, I’m making minor changes on the MAC as well.

I would appreciate any insight into workflows using both Windows and MAC dev machines, as well as best practices for ssh keys to push updates to the new ionic pro service.

1 Like

Ionic Pro is a hosted and closed source service, so there is not much we, the community, can help you with.
There is a FAQ and common/known issues at
Official documentation is at and
You can - and should - contact support at

Thanks for the links. The whole Ionic Pro thing seems pretty new, and I just figured there might be some folks in the community who had a similar setup, and who might be able to share their experiences.

1 Like

Just a quick update here. I ultimately configured a separate set of keys for my MAC dev box. I can connect fine that way to make commits from the MAC. You should also be able to use previously configured keys, but you will need the file to reference in the command line as follows:

ionic ssh use --PathToKeyFile

I am still waiting for a response from Ionic Pro support regarding best practices. I am also waiting on a couple other questions to be answered, so their support services have not been lightning fast at this point, like more than 48 hours out, but I’m still hopeful.