[TYPO3-caretaker] caretaker_instance mass installation

Martin Ficzel martin.ficzel at gmx.de
Tue Jun 28 15:18:23 CEST 2011


Am 28.06.11 11:03, schrieb larsen007 at web.de:
> Hi,
>
> I lately read an article about caretaker in T3N and I am currently testing it. So far, it
> looks very promising and I also saw that there has already been some discussion about how
> to get multiple sites into caretaker
> (http://lists.typo3.org/pipermail/typo3-project-caretaker/2010-August/thread.html)
>
> I hope that the original author reads this as I want to know if any of those scripts you
> used could be made public? Those would surely be helpful for a lot of people.
>

Hi Lars,

the scripts we use check very specific conditions on our machines. I see no benefit in 
making them public. We connect those scripts to caretaker via caretaker_rsml which is in 
svn. Caretaker rsml calls a url and reads the state and result message from the returned 
xml. This way you can connect nearly every script you can write to caretaker.

The remote mass-installation of extensions is not our business since we want caretaker to 
stay read-only for security reasons.

We manage updating of caretaker_instance in a very simple way. We have a central folder on 
each machine where we have subfolders for each major typo3core and each often used 
extension. Inside the folder is a symlink "current" which points to the latest an greates 
in the selected branch. If we want to update caretaker_instance on one machine we only 
have to copy the new source in those folder and adjust the target of the 
"current"-symlink. In all TYPO3 Instances we add only symlinks to the central current 
symlinks of typo3-core and caretaker_instance. This way updating a machine with multiple 
typo3 installations is a 2-liner.

Regards Martin


More information about the TYPO3-project-caretaker mailing list