I'm in a Team with bitbucket account, and I've created a repo, say
The project is on remote server and all member's team should be able to push and pull using a common ssh key.
I've tried to add an ssh key to fashion_repo via
Settings > General > Access keys
but as advised I can gain read-only (pull) and not write (push) permissions.
Since my only need is to make git push and git pull without using my personal account (many developer on same project) and would that all developer could use same non-personal ssh key, what can I do?
I know I could create a new account as "server account", but I hope there's a better solution.
and thanks for your reply.
One thing I don't understand:
For you to use common keys, you'll have to generate one and send the private key to each team member
The one you suggest to generate should be generated in my personal account? that is I have to share a personal ad-hoc SSH KEY with other members? There's no chance to associate an unpersonal SSH KEY about that repo?
For my goal the shared SSH Key should be on my shared server but my problem is one:
where can I set that key into bitbucket repository's settings so that it could be possible perform both PULL and PUSH? (not read-only)
Here there's settings available with my account:
Settings > General > Access keys is read-only, and I think that PIPELINES section is used to set pipelines, that is operation as test and build my project... I just want to be able to make PUSH command.
Be patient, please!
Your only option here would be to set up an SSH key; associate it with a specific user account; and distribute the private key.
I really do not like that option, though, because the act of sharing the private key is inherently insecure, and because you'll need to change the key every time your team membership changes. Far better to have your team members set up their own individual keys and do pushes and pulls on their own.
I was afraid it was just like that...
The problem is that all team (5 persons) access the server with same account (not best practice, I know), so we can't use more than one key.
Currently my solution is to have modified the repository's URL in:
so each user can push and pull inserting it's username and password every time... uncomfortable, but a good compromise.
After some research, I found that is the way to create the ssh key correctly. And add the ssh key to the team, no at the settings project.
Paste the text below, substituting in your GitHub email address.
ssh-keygen -t rsa -b 4096 -C "email@example.com"
This creates a new ssh key, using the provided email as a label.
Generating public/private rsa key pair.
When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
Enter a file in which to save the key (/home/you/.ssh/id_rsa): [Press enter]
Enter passphrase (empty for no passphrase): [Type a passphrase] Enter same passphrase again: [Type passphrase again]
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs