Comments on: Using Git to Maintain Your Website

By: Daniel Miessler

Daniel Miessler — Fri, 29 Jan 2010 15:53:20 +0000

With git you have a history of all changes, and you can roll back to
specific points.

By: Frank C. Tannehill

Frank C. Tannehill — Fri, 29 Jan 2010 09:27:43 +0000

Hello Daniel! Can you please explain why it's better to make the changes offline rather than directly on the site? Why is it better to change the copy and then upload it? Does it has something to do with how the search engines see the site? Can it affect the rankings?
___________
Frank Tannehill - domain

By: A tcpdump Tutorial / Primer « The world apart

A tcpdump Tutorial / Primer « The world apart — Tue, 19 Jan 2010 17:44:52 +0000

[...] Managing Your Website With Git [...]

By: git top links: 2010-1 « git blog

git top links: 2010-1 « git blog — Wed, 13 Jan 2010 23:43:58 +0000

[...] Using Git to Maintain Your Website (42) [...]

By: dowlie

dowlie — Tue, 29 Dec 2009 14:24:35 +0000

hey

thanks for the tip. I'll try it

By: Destillat KW50-2009 | duetsch.info - GNU/Linux, Open Source, Softwareentwicklung, Methodik und Vim.

Fri, 11 Dec 2009 06:18:49 +0000

[...] Using Git to Maintain Your Website [...]

By: Using Git to Maintain Your Website | danielmiessler.com : Popular Links : eConsultant

Tue, 08 Dec 2009 06:27:13 +0000

By: Using Git to Maintain Your Website: http… « Dc's Notes

Using Git to Maintain Your Website: http… « Dc's Notes — Tue, 08 Dec 2009 03:37:21 +0000

[...] Git to Maintain Your Website: http://danielmiessler.com/blog/using-git-to-maintain-your-website [...]

By: Using Git to Maintain Your Website | danielmiessler.com « Netcrema – creme de la social news via digg + delicious + stumpleupon + reddit

Tue, 08 Dec 2009 02:16:09 +0000

[...] Using Git to Maintain Your Website | danielmiessler.comdanielmiessler.com [...]

By: 小鱼笔记 » 使用Git维护你的网站

小鱼笔记 » 使用Git维护你的网站 — Tue, 08 Dec 2009 02:13:01 +0000

[...] http://danielmiessler.com/blog/using-git-to-maintain-your-website 标签: Git tornado.database添加PooledDB连接池功能 [...]

By: Daniel Miessler

Daniel Miessler — Sat, 05 Dec 2009 06:20:45 +0000

Yes, it's a much better way of doing it.

By: Ryan

Ryan — Fri, 04 Dec 2009 21:52:31 +0000

Thank you for your post; it has been very helpful! I am in the process of making this set-up for myself, and it seems that the post-update hook you give has changed yesterday or today; is that correct? The old was:

WORKDIR="/your/live/html/directory/"
export GIT_DIR="$WORKDIR/.git"
pushd $WORKDIR > /dev/null
git pull
popd > /dev/null

And the new is:

cd ../htdocs
env -i git pull

It seems so, but just to clarify, is the new/replacement simply a more efficient way of doing the same thing? Thanks again!

By: Bogdan

Bogdan — Thu, 12 Nov 2009 21:39:04 +0000

I believe there is a significant privacy problem with “live” html directory being a git repository – it contains the .git directory, which could be copied by a malicious (or just curious) user to gain access to private data (database access credentials in the simplest case).

Of course, this requires AllowDirectoryIndexes (or whatever is the correct name) set to On, but still…

By: Jason Diehl

Jason Diehl — Thu, 27 Aug 2009 20:51:09 +0000

I've been looking around at different topics on using Git to maintain a website. My Problem is that I don't understand how with all the branching and everything else to actually make it effective. For example, I have my main branch, which is my live site, set it up so that when it's pushed it updates the live site. Then I can have a development branch for trying out changes and such, this is awesome, but after I make the changes how do I try them out for like a PHP dynamic site? I assume I would create another repo for development that updates a development server or space, so I make my changes, push to the dev, then I can test them there? Okay then with git again it's really easy to branch again for maybe a quick patch, or to try another little change out. But where do I push that to test those changes? Do I need to create yet another repo that updates another web space somewhere, which would only be short lived, so seems like a lot of work. I guess I really really like the idea of Git, but don't understand how to utilize the branching and still be able to test changes. Or do you just not use branching so much in this kind of situation? Or is it really like a few comments I've seen online where people say "it's stupid to update a website with git"?

By: επιστροφή στις “στατικές” σελίδες; – vrypan|net|weblog

Sat, 08 Aug 2009 22:45:41 +0000

[...] να βρείτε παρόμοιες ιδέες πίσω από posts και projects όπως: – Using Git to maintain your website [2] – Git website howto – How to Maintain Static Sites with Git & Jekyll – Blogging Like a [...]

By: r0s

r0s — Tue, 04 Aug 2009 05:45:29 +0000

A little more info...
Git can manage multiple projects under a main repository called Submodules.
With this and branches, there seems to be no need for the bare repo.
This is the way I'm planning to use it.
If I find problems I'll try to report back.

By: r0s

r0s — Tue, 04 Aug 2009 04:01:56 +0000

@ Yann
That's my thought too.
Shouldn't you simply branch your project at the main repo, instead of having an almost live copy on the server?
Also it seems counter to the distributed model of Git, that is, each developer has the whole project, so they can pull from each other to see code and collaborate.
That second point may be quite misinformed.
Anyone know the answer?

By: Yann

Yann — Fri, 17 Jul 2009 05:10:51 +0000

I'm in the midst of converting to Git and looking around on the web, I see that everyone seem to do dev -> bare repo -> live site. I"m new to git and there's one thing I don't understand... Why not make the live site the repo, what's the use of the bare repo in the middle?

Any clarification on that much appreciated :)

By: Yann

Yann — Fri, 17 Jul 2009 01:10:51 +0000

By: Anthony

Anthony — Tue, 07 Jul 2009 18:49:56 +0000

post-update must be in html.git/hooks, not html.git.

By: Jed Koops

Jed Koops — Sun, 21 Jun 2009 05:08:18 +0000

You may want to remind users that when they issue the clone command (git clone ssh://yoursite.com/path/to/html.git), they need to specify the full path to their git repository. I was getting the “fatal: The remote end hung up unexpectedly” error until I realized I was not specifying the full path on the remote server filesystem.

By: David

David — Mon, 25 May 2009 17:29:21 +0000

Great tutorial. Thanks. Found similar at http://joemaller.com/2008/11/25/a-web-focused-g....
Not sure what are the advantages of using in hooks 'pushd' / 'popd' or just 'unset GIT_DIR' which way is better?

By: Daniel Miessler

Daniel Miessler — Wed, 06 May 2009 22:54:48 +0000

I've not implemented this myself, but there is a .gitignore file that you can use for this. I'd have to check out the usage, though…

By: Tatlar

Tatlar — Wed, 06 May 2009 22:51:52 +0000

Can you outline how you would use this approach if you have a typical website with lots of files, images etc that should be ignored? I have a site that has a large directory that is constantly updated with a bunch of html and gif files generated elsewhere and rsynced over that should not get version controlled.

Do I need to add them into the repo in the git init? And then ignore them thereafter?

By: Daniel Miessler

Daniel Miessler — Wed, 06 May 2009 18:54:48 +0000

I've not implemented this myself, but there is a .gitignore file that you can use for this. I'd have to check out the usage, though…