We are working on a project to create a J2EE + GlassFish-based application server in order to update the way we work in our company.
In this environment, two programmers will work on the same project, and we chose Git as a versioning tool.
My question is: To use Git, do I create an account for each programmer + an account for the server? I use an account only as a project repository? I am a layman to use versioning system, I have read a lot but still did not get the idea right in my head.
The ideal is to have an account for the company, not for the server. If the company has other projects later, you can create one repository per project.
With a single account for the company you can then use cool things like Jenkins or Hudson, which are tools that help automate various tasks and integrate with version control systems.
As far as versioning is complicated to understand, in my experience people only really understand it after using and feeling the benefits it brings in practice.
To use GIT, it does not necessarily have to be with Github, there are other platforms that make Git available as a Version control, such as Bitbucket, Gitlab, Visual Studio Team Services.
As Renan said in another answer, you can use a number of other tools, as he himself quoted, Jenkins, Hudson, etc.
I know a lot about Visual Studio Team Services, and so my suggestion to you is to use this tool, by the following points:
These functions above, you can use for free in VSTS in the case with up to 5 developers. You can also, by paying the part, have your nuget server and private npm.
Bacana, is that this works not only for Microsoft technologies, you can manage for example your Java project, automate builds, and Deployment of Java applications, including using linux servers for build and / or deployment target.
On learning git, there is a lot of good stuff on the internet, such as:
If you want to know more about VSTS, I have a playlist on my channel about it
