See my two cents inline
On 1 Jul 2015 20:01, <m...@joketube.tv> wrote:
> What are rules to follow when you plant to use git for developing a web
site? Firstly I tried to create lots of branches for each part of a web
site (index, authentication, member page) but soon I faced lots of problems:
> 1) What I should do with database which is continuously modified over
time (should I upload it to git)?
Tracking database content with Git doesn't seem to be a good idea. What you
may need instead is schema migrations, e.g. track the file containing
queries necessary for adding storage space for the new features
> 2) Should I use single or multiple branches for separate pages (index,
authentication and member pages)?
I don't think so. There are many approaches here, e.g. you may want to
stick to the development model you already mentioned: one branch for every
feature. But even that may be unnecessary, depending on your workflow.
> 3) How can I automatically deploy web site if it contains database's and
mail gateway's credentials?
First things first: Git is not a deployment tool. There are many deployment
tools out there that can utilize Git, though.
Also, storing different credentials in the repository is usually a bad
idea, especially if your repository is public (e.g. hosted on GitHub). You
may want to create a default config file with your development server
credentials, and at the end of this file include an untracked config which
overwrites the necessary values.
> It's a bit easier to use git when you already have a web site. In that
case we simply create new branch for each update. I guess there are no
unique solution for my case and each and every person finds its own way to
use git but any suggestion/sharing experience will be highly appropriated
> Thanks in advance
> Yehuda Katz
> p.s. I do not use frameworks during web site development process
> You received this message because you are subscribed to the Google Groups
"Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.