[TYPO3-dev] TYPO3 and svn

[Adrien Crivelli]

"Git stores all changes in 1 .git directory on the root-level of your
project, so you can update extensions using EM without any issues."

I disagree on this one. The issue with updates via EM is that you are no
longer in control of your extensions (and their versions). No matter what
vcs you use, if you don't use it for everything in your project, then you
lose a lot of benefits.

Unless if you update via EM and then commit the update to your vcs. But then
you duplicate the extension "repository" within your own repository and
still miss a lot of benefits vcs could give you.

I think the only clean solution, vcs-wise, is the use of externals (or
submodule for git). You know exactly what version you are using, where it is
coming from and its whole history (the "official" one, not your own update
history).

Anyway, I agree on git vs svn :-)



On 9 June 2011 07:08, Loek Hilgersom <loek at netcoop.nl> wrote:

> Hi Frank and others,
>
> It could be worth having a look at git. Git stores all changes in 1 .git
> directory on the root-level of your project, so you can update extensions
> using EM without any issues. We use git to store entire projects, starting
> one level up from the site-root. This has the advantage that you there is no
> .git inside the site-root, and the repository also has place for things you
> don't want to have in the site-root (we store things like different server
> configurations, dev-data sets and deployment scripts in there).
>
> Having .git one level above the site root means you could also use it on
> the production server (we don't yet, but I do see some advantages like those
> mentioned in this thread).
>
> Anyway, having worked with git for a few months now I am not going back to
> svn anymore. It's definately an upgrade especially if you're working in
> teams and using multiple branches etc.
>
> Cheers,
> Loek
>
>
> Op 01-06-11 13:39, Frank Mey - NEW.EGO schreef:
>
>  Hi,
>>
>> as a developer I totally agree :), thanks for laying out your concept,
>> it will be added to our discussion of versioning TYPO3 projects :).
>>
>> Regards,
>> Frank Mey
>>
>>  -----Original Message-----
>>> From: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-
>>> bounces at lists.typo3.org] On Behalf Of Adrien Crivelli
>>> Sent: Wednesday, June 01, 2011 1:09 PM
>>> To: List for Core-/Extension development
>>> Subject: Re: [TYPO3-dev] TYPO3 and svn
>>>
>>> Yeah, you're totally right. I have a background of software developper
>>> not
>>> website integrator or designer, so it doesn't bother me at all, but this
>>>
>> may
>>
>>> not be convenient for everybody. My focus is to get a system as stable
>>> and
>>> reproducible as possible. I cannot stand developping on production
>>> server,
>>> so reproducible environment really is a must-have to me.
>>>
>>> As you mentioned, it unfortunately comes with some drawbacks for "power
>>> users" who should not (but yet could) install/update extensions via
>>> Extension Manager.
>>>
>>>
>>>
>>> On 1 June 2011 12:39, Frank Mey - NEW.EGO<mey_mailings at newego.de>
>>> wrote:
>>>
>>>  Hi,
>>>>
>>>> sounds good, but you loose the benefit of a TYPO3-Integrator / - Admin
>>>> doing Extension updates through the TYPO3 backend, if I understand
>>>> your concept right. For dev installations this concept seems fine,
>>>> though.
>>>>
>>>>  -----Original Message-----
>>>>> From: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-
>>>>> bounces at lists.typo3.org] On Behalf Of Adrien Crivelli
>>>>> Sent: Wednesday, June 01, 2011 11:38 AM
>>>>> To: List for Core-/Extension development
>>>>> Subject: Re: [TYPO3-dev] TYPO3 and svn
>>>>>
>>>>> Hey,
>>>>>
>>>>> Here we use SVN to version everything starting from the parent
>>>>> folder of 'htdocs' (or 'public'). For extensions we use svn:externals
>>>>>
>>>> to
>>
>>> "import"
>>>
>>>> extensions and manage their updates very easily.
>>>>>
>>>>> So the layout is something like:
>>>>>
>>>>> mysite/
>>>>>    trunk/
>>>>>       scripts/<= a few useful maintenance scripts which should
>>>>> never be reached over http
>>>>>       htdocs/
>>>>>          fileadmin/
>>>>>          typo3/<= symlink to a centralized checkout of typo3
>>>>>          typo3conf/
>>>>>             ext/<= here goes all svn:externals definition to import
>>>>> 3d
>>>>>
>>>> party
>>>>
>>>>> extensions
>>>>>                customextension/<= an custom extension only for this
>>>>>
>>>> website
>>>>
>>>>>
>>>>>
>>>>> The benefit of this structure is that a single checkout get you the
>>>>> whole website, including its extension with their exact version. We
>>>>> could also
>>>>>
>>>> use
>>>>
>>>>> svn:externals for typo3 core, but in our case we have severals
>>>>> websites running on typo3, so we one centralised instance which is
>>>>> easier to
>>>>>
>>>> maintain.
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 1 June 2011 09:39, Jesper Goos<jesper at goos.dk>  wrote:
>>>>>
>>>>>  Hi
>>>>>>
>>>>>> I have often wondered what the best way is to maintain a SVN
>>>>>> repository for a site developed with TYPO3. Do you have any
>>>>>> hints/links
>>>>>>
>>>>> for
>>>>
>>>>> that subject?
>>>>>
>>>>>>
>>>>>> What is the best practice for this?
>>>>>>
>>>>>> Thanks a lot!
>>>>>> Jesper
>>>>>> _______________________________________________
>>>>>> TYPO3-dev mailing list
>>>>>> TYPO3-dev at lists.typo3.org
>>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>>>>>
>>>>>>  _______________________________________________
>>>>> TYPO3-dev mailing list
>>>>> TYPO3-dev at lists.typo3.org
>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> TYPO3-dev mailing list
>>>> TYPO3-dev at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>>>
>>>>  _______________________________________________
>>> TYPO3-dev mailing list
>>> TYPO3-dev at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>>
>>
>>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>