Git best practice with new database

Question

Question regarding Git best practices. When making a major new version of a project (in my case it's a Codeigniter project) I am faced with two options:

Create a new branch (e.g. branch version2)
Create a copy of existing project folder and make it a new git project.

Advantage of 1): development may be ongoing for version1 branch, so it will be easier to merge them at the end.

Disadvantage of 1) (and therefore advantage of 2)): version2 will be using an entirely new database, and will (at first) be hosted on a different staging server. Since my config files are not part of the repository, each time I want to switch between branches I'll have to manually edit the database config file.

The disadvantage of 1 situation... how many times do you expect this situation to actually happen? — gerosalesc, Jan 06 '16 at 16:56
No, not using github -- I don't expect situation1 to recur very often. — GluePear, Jan 06 '16 at 17:49

score 0 · Accepted Answer · answered Jan 06 '16 at 16:52

0

You should probably create a new branch and if you don't want to manually edit the database config file each time, you have the possibility to clone several times your project. Hence, merging the two versions will probably be easier than solution 2).

answered Jan 06 '16 at 16:52

L. Meyer

2,531
1
20
23

Yes, this is the conclusion I've come to as well. – GluePear Jan 06 '16 at 17:50

score 0 · Answer 2 · edited May 23 '17 at 12:31

If you are using Github/Bitbucket/VisualstudioOnline or any other service like this, I would use Forking instead of branching, the difference between branching and forking are mentioned in this SO's question but it is important to state this few things here:

If you are working in version 2 You won't be able to push changes directly to version 1 repo but you would need to create a new Pull request.
To keep the version 2 repo up to date with the original one, You will need to either add the original repository as an additional remote repository on your local repository or use Github sync tool.

score 0 · Answer 3 · answered Jan 07 '16 at 12:18

As you are talking about GIT best Practices, I would like share your some of my points.

All files should be present in Git repository( As currently, your database config files are not stored in GIT Repository)
No Branching workflow is used ( Currently no branching workflow is followed by you which is not correct)

Solution:

Git Should contain all files(Even your database files)
Feature branch workflow should be used.

Feature branch workflow provides solution to both your problems , where you can create new release branch and deploy it to N1 server and release branch 2 to N2 server with different databases.

Also as CodeIgnitor is used you can define N number of environment and specify your settings within it. This will help you to specify different databases for different servers/environments.

Git best practice with new database

3 Answers3