CODEWITHSUNDEEP
phpversion-control
typicalnoob
typicalnoob

Reputation: 11

Version Control by Making different folder

I'm working from a remote site. In the jungle to be precise. My way of version control is for every upgrade, I will copy the whole current file to a new folder and name it based on the version and upgrade code on the main folder. Is this right?

Upvotes: 0

Views: 36

Answers (2)

simbabque
simbabque

Reputation: 54323

No.

Your approach will give you some kind of backup, but not professional version control. The difference is that your process is a lot more manual and does not document any changes you made. You cannot see when you made changes, or why.

Version control systems like git are vastly superior to that.

For most version control systems in general it doesn't matter where you are, or where your team is, as long as you have network in between.

A good approach would be to read up on git either on the official git-scm website, or maybe over at Atlassian. Those should get you started on how basic use works. If you want a bit more explanation of how its magic works, I suggest the excellent talk Git for ages 4 and up by Schwern.

Because deployment has been menitoned also, I would like to add that how you deal with your finished product doesn't really matter to version control. But the version control software can be used by deployment systems to get the newest version, which is convenient.

Upvotes: 1

Swakeert Jain
Swakeert Jain

Reputation: 776

No. This is not a professional way of working with version control. You should use GIT, SVN o something similar. Your approach is only creating redundancies on your local machines and wont help you identify any changes made in different versions. GIT stores differences and therefore is helpful in keeping check of what exactly changed between two versions and is therefore actually helpful in debugging.

Upvotes: 2

Related Questions