Disable some remotes for a git repository ?

Answered

In my project, I work on a repo which has three remotes, one is on my own Gitea forge and two others are bare repos where I push to deploy my code on staging and live web servers via post-receive hooks :

[remote "origin"]
    url = https://gitea.*****/*****.git
    fetch = +refs/heads/*:refs/remotes/origin/*
[remote "staging"]
    url = ssh://*****@xx.xx.xx.xx:/var/www/*****.git/
    fetch = +refs/heads/develop:refs/remotes/staging/develop
[remote "prod"]
    url = ssh://*****@xx.xx.xx.yy:/var/www/*****.git/
    fetch = +refs/heads/master:refs/remotes/prod/master

The ssh connection to these bare repos (staging and prod) is done via a password and is filtered on my WAN IP.
(I'd prefer an access via private key but I'm not responsible for the hosting of the web servers...)

It seems PhpStorm tries to connect to these bare repos without my password, and this could be the cause of my WAN IP being banned sometimes ("Too many authentication failures").
Plus, it has no sense since they are just bare repos.

How can I tell PhpStorm to not connect to these two bare remotes, but still being able to interact with the main remote (on my Gitea) ?

If it's not possible, how can I store the SSH password in PhpStorm in a relative secure way ?

Thanks,

1 comment
Comment actions Permalink

Nevermind, the problem wasn't linked to PhpStorm but to the server's configuration.

0

Please sign in to leave a comment.