[TYPO3-dev] Best practice: How to store a complete TYPO3 installation in git

[Andy Grunwald]

Hey everybody,

i know that many people / companies working with git and TYPO3.
Today i asked me (during a coffee break) which kind of ways are exists to store a _complete_ TYPO3 installation / project in git.

Every problem in development can be solved by x ways. I think this question, too.
But what are advantages / disadvantages of the different ways?

Some (created in 2 min.) thoughts are:

* Store the complete TYPO3 core source in Git?
* Use a "build" script (e.g. to download TYPO3 source or extensions from TER, ...)
* What about the database / content / changes? Tools like Liquibase [1]?
* What about content assets? Set them to ignore?
* What about TYPO3 Source updates?

I think there are many more questions.

The way of storing a project into git it direct related to the way to deliver it to the server.
What are solutions for this?

A short google search opened a stackoverflow post [2]
But this far from "complete".

Maybe some of you can post their experience and the way how you work with git and TYPO3 projects (private / customers).
E.g. 
* What about your .gitignore? 
* What structure do you use? 
* Are custom scripts involved? 
* If yes, what does these custom scripts do?

If there are some useful answers we / i can create a full "Best practice" post / topic in a Blog or on Buzz about this topic.
In my opinion this is a topic which is interesting for many people.

If someone of you using Subversion, the same question can be applied to this CVS as well.
So your answer is welcome, too.
But please notice at the start of your post which VCS you are using.
THX :)

Andy!

http://www.liquibase.org/
http://stackoverflow.com/questions/11905360/how-best-to-manage-typo3-installations-using-git