[git-users] Re: website deployment through git

2014-05-31 Thread bastilani


Il giorno venerdì 30 maggio 2014 10:21:58 UTC+2, Pierre-François CLEMENT ha 
scritto:
>
> The easiest would be to have multiple branches and remotes on your local 
> repo. Something like develop ("developing"), release ("testing") and master 
> ("production") should do the trick. I've taken the branch names from Nvie's 
> git-flow branching model 
>  which, if you're 
> not using it already, I strongly advise you try.
>
> Then add a git-remote for each one of your servers (developing, testing 
> and production), and you'll be able to push whatever branch you want to 
> whatever server you want.
>

Thank you both for your answers.
Yes sure, I'm following nvie's git-flow.
But I didn't add git remote for each servers, because actually there's one 
server with some virtual host configured, so just the post-update is enough.

Thanks a lot 

-- 
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.


[git-users] Re: website deployment through git

2014-05-30 Thread Thomas Ferris Nicolaisen
Generic answer/advice: http://gitolite.com/deploy.html

-- 
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.


[git-users] Re: website deployment through git

2014-05-30 Thread Pierre-François CLEMENT
The easiest would be to have multiple branches and remotes on your local 
repo. Something like develop ("developing"), release ("testing") and master 
("production") should do the trick. I've taken the branch names from Nvie's 
git-flow branching model 
 which, if you're 
not using it already, I strongly advise you try.

Then add a git-remote for each one of your servers (developing, testing and 
production), and you'll be able to push whatever branch you want to 
whatever server you want.

-- 
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.


[git-users] Re: website deployment through git

2014-05-29 Thread bastilani


Il giorno domenica 25 maggio 2014 16:05:56 UTC+2, bast...@gmail.com ha 
scritto:
>
> Hi,
> I'm starting to use git. I need it to manage a website.
> Up to now, on my server (linux, debian based) I configured a bare 
> repository (/opt/git/project.git/).
> I added a post-update hook, in order to checkout automatically to 
> /var/www/website.ext/public_html/ and all it works fine.
> Now I would like to improve developing process.
> I would like to have some environments (and related virtual host), 
> "developing", "testing" and "production" and manage properly all deployment 
> on each environemnt based on needed.
> I mean, I would like to create a file, for e.g. index.php, the first step 
> will be to push on developing environment (accessible through a 
> virtualhost: /var/www/dev.website.ext/public_html). then when it's ready 
> move it on testing environment (accessible through a 
> virtualhost: var/www/testing.website.ext/publich_html) and at the end of 
> the process deploy on production (/var/www/website.ext/public_html/). Each 
> environment should be managed with git.
> But my question is, which is the best approach? Have I to create 3 
> different repositories (one for each environment with hook set)? Or can I 
> manage this with a single repository?
> I'm looking in the net with google, but up to now I'm not found anything 
> about this scenario, or maybe I'm searching with wrong keyword, I don't 
> know.
> Please, may you help me?
>
> Many thanks
>


I found an answer to my question.. one repo and two branches and 
post-update hook to deploy on each virtual host.

-- 
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.