A
A
axel2017-07-08 02:13:41
Bitbucket
axel, 2017-07-08 02:13:41

Can I set a separate password in Bitbucket for the user who shares my repository?

Such a situation: we are working on a project with a team of several people. The code when we push everything to my personal repository on bitbucket. At the same time, each of the team members should be able to upload changes to the existing server at any time. On the server, connecting via ssh, git pull origin master is written in the console - and when git asks for the password from the repository, the password from my personal account is entered! The password is known to everyone, but this is not very correct. Is it possible to do something for each user to whom I gave access to the project - to set some kind of his password so that he can use it to pour his changes to the server?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Stanislav, 2017-07-08
@Antoine

You went the wrong way in the first place. You need to give access to a private repository, this can be done in two ways.
then make this repository the repository of this team. Well, accordingly, your colleagues will have to register on Bitbucket, and you will have to invite them to the team.
After that, you can safely change your password. You'll have to fiddle around a bit with the settings, plus, for example, you can make it so that only you can approve a pull to your repository (a.k.a. a pull request), but those are more pros than cons.
This is about the organization of work with Bitbucket itself. Further, as to "to fill in changes on the operating server". If I understand you correctly, then in this way you have implemented the deployment of your project from your repository to the server where your application is running.
This is not quite the right way, or rather, it is completely wrong, since this can only be done on test environments, where you can tweak something, wait until the actual pull happens, and so on. Try to use something like Capistrano, or any other similar utility. This will solve the issue with the storage of passwords, and with everything else. As a last resort, make authorization through a key, and not through a password. In this case, by adding it once, you will forever forget about entering your account password when loading your application. You can learn more about this here , and in general, googling about bitbucket ssh key.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question