[TYPO3-dev] TYPO3 and svn

[Adrien Crivelli]

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
>