[TYPO3-dev] development process

[dan frost]

As a matter of interest, this is something we've overcome by using a 
combination of:
- migration scripts similar to RoR
- versioning the database structure outside of the TCA/TYPO3 DB 
definitions (which isn't really well structured)
- ...and versionining the data in separate files

Big problem with TYPO3 is that the DB are still extremely badly 
organised, despite all our best efforts(!). So the best thing is to 
apply the most atomic versioning and build control you can to the tables 
to reduce the problem space when merging databases.

dan
3ev.com



Martin Kutschker wrote:
> Andrew Tabachyn schrieb:
>> Hi,
>>
>> Thank you for your answers. We are going to use Ant for builds on our 
>> test environments, but still I have open question how to deliver local 
>> changes what was done in database, for example several pages has been 
>> added. Only one solution I can see right now - do the same on test 
>> environment manually after Ant based delivery.
> 
> When I develop an extension (writing PHP) I usually have a complete test 
> enviroment that is not duplicated as such. So I only sync the PHP code 
> but not the DB records (pages, etc).
> 
> OTOH if more TYPO3 coders (TS and ext.) work on one project I wouldn't 
> use multiple databases at all. Maybe you could make a setup where you 
> have on DB that is the master and replicate to your dev machines. So new 
> pages must be created on the master server but you could add local 
> content (not synced) on the individual machines.
> 
> Masi