[TYPO3-dev] TYPO3 and SubVersion?
Tobias Pinnekamp
mail at tpinne.de
Thu Jul 6 09:35:12 CEST 2006
Joerg Schoppet schrieb:
> Jigal van Hemert wrote:
>> Hi all,
>>
>> With all our other sites we use the combination of Komodo and SubVersion
>> (with a few extra scripts) to edit source code, store changes in a
>> versioning system and have a copy on the development server with
>> relative ease.
>>
>> Is there anyone with experience on using SubVersion with TYPO3? Storing
>> the source code in SubVersion is easy, but are there any tricks to
>> manage changes in TypoScript, database records, etc.? We always use a
>> development server, an accept server and a production server for each
>> site, but moving changes to accept and production is far from simple
>> when it comes to non-source code items.
>>
>> Regards,
>>
>> Jigal van Hemert
>
> Hi Jigal,
>
> the only thing we managed to get in svn were the TS-Templates:
> - Save the content of your constant-field and setup-field in different
> text-fiels
> - only include [1] the following in your templates (e.g.):
> <INCLUDE_TYPOSCRIPT: source="FILE:
> fileadmin/templates/ts/generalConfiguration/constants.txt">
>
> This has some advantages compared with writing directly in the template:
> - You can use any editor you like with all its features (e.g. tabs)
> - You can put the files under version-control
> - Because you can "include" as many files as you like, you can separate
> different aspects of the configuration in different files (reuse)
>
> Drawback:
> - You still have to manually include this in the DB
>
> [1]
> http://typo3.org/documentation/document-library/core-documentation/doc_core_ts/current/view/1/2/
>
>
> Regards Joerg Schoppet
Hi Joerg,
that sounds intersting. But how is the performance? It is recognisable
slower than storing it in the database? I think so, without testing it,
because on every page request the file must be included and read. What
are your experiences?
Best regards
Tobias Pinnekamp
More information about the TYPO3-dev
mailing list