Using Dropbox as a repository for Netbeans 8 projects on Windows

Asked

Viewed 670 times

0

I am using Netbeans 8 in my projects and would very much like to use Dropbox as a versioner. I set up the repository in Dropbox but with the project directory in another way. I may be confusing things, but what is sent to the Dropbox folder is just the directory. git.Inicio o projeto e seleciono o diretório do git

However, the project is not sent to Dropbox, what remains is only the . git which makes it impossible for a person who has access to my Dropbox folder to start the project, update and so on. I looked for tutorials and information, but everything by command line, does it really have to be like this by command line? Sorry I don’t have any code to send.

  • I don’t get it. Git is uploaded or not to Dropbox? You only need it to be able to work as a team in the msm project. Ah, and using Dropbox for this can be a terrible idea, because when synchronizing it does not guarantee the atomicity of the operation, which can completely ruin your repository.

  • It makes me wonder, what goes into the version repository is only . git? the problem is that when I try to clone not right, the project files are not there.

  • 1

    Yes, just git is enough. You must be making a mistake in your process. You need one. git local, in the same folder as your project, and vc can have a remote, which you update via push

  • The. git in the project location exists yes, I only used Netbeans features, I didn’t try via command line, I’d better try per command line?

  • 4

    Whatever, but at some point you need to push to update the remote, in your case in the folder of Dropbox. Ah, and consider not using Dropbox for this, see the bitbucket that offers free private Positions.

  • 2

    I didn’t know the bitbucket, my first idea was to use Dropbox because it was free. Your tip was worth the year, rsrs.

Show 1 more comment

1 answer

2


One of the main advantages of Git is the fact that it is a distributed versioning tool. That is, each developer can contribute code to other repositories and at the same time can maintain a public repository on which others can base their work and which they can contribute. [1]

The idea of using the Dropbox as repository centralizer, allowing other people with access to it to also work on the project is not bad, but the result may not be what you expect. There may be a risk that two Velopers are using at the same time, and one commit annul the other.

Work with the Git using a remote repository (disregarding Dropbox, Onedrive, etc.) is ideal in these cases. As quoted by Math, the Bitbucket is an option for free private repositories. The Github is also an alternative, being this private only in case of signing a plan.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.