[TYPO3-dev] Development/Integration/Staging/Production Practice for TYPO3

[Rens Admiraal]

Hi Ben,

I've been searching for this for a while also, but didn't really find
something good (or didn't search good enough :p ). I've once found a
synchronization module (treesync as I remember correctly) which seemed to
offer the ability to synchronize 2 databases. But after emptying someones
productdatabase I stopped using that one :-)

For now we use a structure in which we add the entire project to SVN, and
configure Typoscript in txt files... This makes it also possible to let SVN
merge changes of multiple developers in the same typoscript configuration,
which is cool :-) When we keep a close eye on database changes after the
release of a project, and make those changes before a possible upload of the
project, than everything is really fine... But this is a really weak spot of
this procedure...

We are still thinking about some kind of (FLOW3 based) upload tool with
Dev/Int/Stag/Prod structure, which could upload an installation, but no
actual development done yet... Such a tool could export a tagged version
from svn to a temporary directory for example, compare the database, and
copy the changed files to the live location. Some functionality to
synchronize certain tables (like templavoila tables for example) could also
help a lot... 

So, no, we don't have a bullet proof solution yet, but when we keep the
database structure synchronized (which might also be done with external
tools) it seems to work perfectly well... 

I'm really curious to solutions other people use, or maybe it might be cool
to create such an upload tool (if there isn't one already) as a forge
project...

Greetz,
Rens

-----Original Message-----
From: typo3-dev-bounces at lists.typo3.org
[mailto:typo3-dev-bounces at lists.typo3.org] On Behalf Of ben van 't ende
Sent: maandag 29 maart 2010 10:11
To: typo3-dev at lists.typo3.org
Subject: [TYPO3-dev] Development/Integration/Staging/Production Practice for
TYPO3

Heyla,

Today the question was raised to me how companies deal with advanced
Staging.
That means separate Development/Integration/Staging/Production installations
in a structured process for website development that maximizes productivity
and reduces bugs that reach the user. Ofcourse TYPO3 features workspaces,
but that does not deal with new functionality/extensions in a TYPO3 project.
Some former client I once had used a custom script that would skip dynamic
tables when updating the whole installation if I remember correctly. There
where many disadvantages to that procedure as well and it could hardly be
called bullet proof. I did not encounter such a situation where a client
needed that functionality after that. I can imagine however that in a number
of situations this could be interesting.

Are there already any experiences around of having to deal with such a
situation? In what way would this be do-able in a TYPO3 environment?


gRTz

ben
--
TYPO3 Product Manager
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev