On 2 Jul 2015 08:42, "JokeTube.TV" <m...@joketube.tv> wrote:
>
> Thanks for your help Gergely!
>
> 1) Do you mean use manual tracking or is there any automatic ways to do
that?

However you can solve it. I work with the Django framework which provides
automation for it. It's hard to make suggestions without knowing the
details.

>
> 2) Features could be added only when I have something but what should I
do before? Someone suggested to do everything in master branch and create
checkpoint branches for each release (later they could continue its own
development). However is it a good approach for web site development?

This, as I said, depends on your own methods. For my last project I tracked
everything from the beginning on different branches even if they were
instantly cherry-picked back to master. I added authentication on one
branch, registration on another, product listing on a third, etc. The fact
you make a branch for every feature doesn't mean you must have tons of
feature branches at a time.

Working with feature branches doesn't prevent you from having version
branches. However, it is a bit strange for me to have version branches in
web development. Unless you are making a web based product, why would you
have them? For a web service (like, eg. GitHub) use continuous deliveries
(like GitHub). Whenever you think a feature is ready, deploy it. You may,
of course make some feature locks if feature A is not fully usable without
feature B, but we are touching development methodology waters here.

>
> 3) Thanks, that's a good idea! That way each developer will have their
own config file.
>
> Waiting for your reply,
>
> Yehuda Katz
>
>
> Thursday, July 2, 2015, 2:51:52 AM, you wrote:
>
>
> See my two cents inline
> On 1 Jul 2015 20:01, <m...@joketube.tv> wrote:
> >
> > Hello,
> >
> > 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 a topic in the
Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/git-users/aAMiqiMtC8I/unsubscribe.
> To unsubscribe from this group and all its topics, 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 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 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to