We have a problem here in the office that is to use a file that the colleague is already using, and save and thus lose the file, does anyone know of a solution? we use Brackets and Sublime text if it is some plugin helps a lot!
Tool to work in a group [closed]
-2
asked by anonymous 10.05.2016 / 18:50
2 answers
3
0
Look, when I read your question I find this situation strange. How do you say that you develop team web and do not understand a simple process like this?
Even if you did not use a versioning control that would be ideal, at least understand that, you do not edit files remotely if you need to keep the file open for long periods of time as is the case of development activities. Because if the remote machine gives you a problem you are not seeing what is happening. Imagine that the remote machine receives a power surge and restarts. You will not be able to save your work and even if this does not happen, someone who opens the same file will conflict with yours. The minimum would be to copy the remote file to your machine and send it at the end of the edit at the cost of someone else having sent it before and could lose its file. How it ended up happening.
But that's not the way to go. The right one for group development is to use a versioning control system such as Git that the tkmattos mentioned. I also recommend Git. He is excellent. But there are more like CVS, Subversion, Mercury and others.
Versioning control systems work like this: you create a repository and each person sends 'modifications' to that repository. Eg: initially you put index.htm, index.css and index.js in the repository. There a developer includes a rule in index.css and sends it to the repository. The versioning control allows you to not only see the current version, but also all modifications made such as identifying who did it, how to view past versions of the whole project and much more.
Some even have more advanced functions like creating "branches". It works like this: you will develop a bug resolution. There you create a separate development branch while the rest of the team continues to work in the core business. You will then have all the history and versioning functions on a separate branch without being confused with the rest of the team. So when and if your version is all ok, you "merge" your branch into the main branch of development.
Git also allows the creation of local repositories, which then send their changes to a central repository, among many other functions that would be too long to describe in a response like this.
How you can see this kind of technology is essential for group development. You can use all these functions only on the command line. And you better know the command line. But I recommend that you use an IDE that allows the complete integration of all these functions. The one I can recommend is the one I use: Eclipse. Few softwares are more complete than it. Maybe just the VIM (but there is also cowardice, the VIM is not a software is an experience: D).
It also has a plug-in that is a must for group development. Mylyn. It connects to a task repository and saves the history of the files that were opened for each task performed. So, if you complete a task and then you or someone on your team needs to redo something about that task you have all the files that were changed by who performed the service in 1st place. Practical right?
In addition to the excellent links that tkmattos passed that are already great for you to learn Git I want to pass this one of a very nice game to learn git that happened to me these days:
10.05.2016 / 19:39