[TYPO3-english] Import-export of *.t3d

[bernd wilke]

Am 25.05.15 um 01:07 schrieb Christian Reiter:
> Hi Bernd,
>
>  > looks very powerful. and maybe a better solution than workspaces in
>  > the  same installation
>
> Depends on what you want to do. Real content staging has its advantages;
> but then workspaces have their advantages too. I Wouldn't want to
> position this solution against workspaces, but if you have a number of
> reasons that make server staging a better solution - there it is!

as times goes by the work flow of companies does change. so the solution 
of workspaces in one installation may be good in one way I see today 
workflow with multiple servers.

>  > is it possible to publish to multiple instances (like a loadbalancer
>  > server array)?
>
> Short answer  - yes.

:-)

[...]
>
> I don't really like the serverarray concept too much though, it "sort of
> works" but really I would prefer to just publish to one remote, and have
> any other remotes be slaves of the first one.

here the admin is against master and slaves because:
what happens if master fails? no slave can update any more (or worse: 
the slaves reproduce the failure of master)

> Just one of the reasons is that when you publish large changesets ( >
> 10.000 records in one publish action can happen) you will have some time
> lag before it gets to all servers.

that always is possible, but can not be avoided if you transfer very 
much data to different machines. independent from way of rollout.

> It's also in principle possible to have many sites in one TYPO3
> installation on the stage server and publish them to different live
> systems, for example:
>
>   stage.site1.com, stage.site2.com are in the same TYPO3
>
>   www.site1.com, www.site2.com are each in their own machine.
>
>  > why is this extension not available in TER?
>
> Using this setup means that you are leaving the "normal" way of doing
> things in TYPO3.

meanwhile there are a lot of extensions which extend the way TYPO3 works 
by default. being able to do this is a very big advantage of TYPO3.

> Also of course it's something that will not do anything at all out of
> the box, you need a setup of two servers first.

I think this is the case in most installations which are a little bit 
bigger than a private website. it is the 'enterprise' part of ECMS

> How to set it up needs close cooperation with the client.
> You might have stage and live servers as different virtual hosts on one
> physical machine, you might have them on separate machines,
>
> When I brought up the topic in the list, the concept of offering this
> kind of capability was not welcomed, to put it mildly.

as stated above: time changes the thinking

> Etc.
>
> There are a lot of extensions for edge cases that don't show up in TER.

yes. I'm sad about it as I consider the central TER a very big advantage 
against other CMSs. And so there is a lot of crap in it (I confess I 
uploaded some too), there are awesome extensions in it I would miss.

> For example one of the clients that kickstarted the publishing tool,
> also wanted to capture all editor actions in fileadmin into a versioning
> system. So each upload, overwrite, delete, rename, etc in fileadmin is
> committed to a VCS right away. This made sense for a special interest of
> the client but really had no place in TER, it's not a general interest.

if you enable hooks to enhance additional features you can make your 
extension mightier and more flexible for others.
and its not so uncommon:
in my current company I configured TYPO3 to:
publish page content as PHP-includes which are distributed with GIT.
not the normal way a TYPO3 installation does work.

bernd
-- 
http://www.pi-phi.de/cheatsheet.html