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

[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!

 > is it possible to publish to multiple instances (like a loadbalancer
 > server array)?

Short answer  - yes.

https://www.youtube.com/watch?v=XZ7Dwa1rvWA is about multiple target 
servers and multidomain. The second part of the video might apply to 
your situation.

With regards to loadbalancers or server arrays I have two situations 
(Most clients get by without LB)

In one case there are two servers running the Apache / PHP workload but 
they use a common (separate) MySQL server und a common file system.
So in that case there is no need to adapt anything. Just publish to one 
DB and FS and everything is done.

In the other case there is a server array.

That does not have anything to do with load balancing though; basically 
there are two copies of the live site (one in Intranet and one in 
Extranet) which share 100% identical code and 100% identical 
editor-created content but behave differently in the FE.

To publish into a server array one needs to define mirror servers in the 
configuration and then a publishing process will iterate through the 
server array.

That means pushing over the database records, and files, etc separately 
to two servers, and also doing things like upating the SolR indexqueue 
for new and changed elements and calling the SolR garbagecollector for 
deleted/hidden items etc. twice.

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.

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.

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.

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.

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.

Etc.

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

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.

Best regards,

Christian


  it is schrieb bernd wilke:
 > Am 22.05.15 um 09:54 schrieb Christian Reiter:
 >> Hi Viktor,
 >>
 >> I put up a small demo of the publishing module to
 >> https://www.youtube.com/watch?v=P5KXSiQeHwE
 >>
 >
 > looks very powerful. and maybe a better solution than workspaces in the
 > same installation than live.
 >
 > two questions:
 >
 > is it possible to publish to multiple instances (like a loadbalancer
 > server array)?
 >
 > why is this awesome extension not available in TER?
 >
 > bernd