But when logged in to Umbraco - it seems like I can only transfer to the first server added, there is only 1 listed in the menu. Am I doing something wrong - or does Courier only support 1 single server to transfer to per environment?
Same issue around here, ended up doing the following to sort out a load balanced configuration:
- Staging -> Production 1 - Production 1 -> Production 2
which is a bit of a pain because we have to publish twice, but until the shared storage can be sorted out to avoid umbraco.config and courier.config locking errors, this will have to do.
We ended up disabling Courier as the "double publishing" quickly descended into chaos, compounded by permission issues on the load balanced servers. It's been running as a distributed simultaneous publish for a while but we'll test Courier 2 soon to see if it can deal better with load balanced environments.
Courier and multiple servers
I have tried adding multiple servers to my courier.config - for example:
<servers>
<server addToContextMenu="true" alias="Staging">cms.staging.mysite.dk</server>
<server addToContextMenu="true" alias="Live">cms.mysite.dk</server>
</servers>
But when logged in to Umbraco - it seems like I can only transfer to the first server added, there is only 1 listed in the menu.
Am I doing something wrong - or does Courier only support 1 single server to transfer to per environment?
hi - I'd love to know the answer to this as well
We're trying to install Courier on a UAT server (which will need to publish to live as well as "transfer" some UGC back to the Dev environments
But have exactly the same problem as Jannick
Help please ;-)
Tim
Would be happy to know as well. Having exactly the same issue.
Same issue around here, ended up doing the following to sort out a load balanced configuration:
- Staging -> Production 1
- Production 1 -> Production 2
which is a bit of a pain because we have to publish twice, but until the shared storage can be sorted out to avoid umbraco.config and courier.config locking errors, this will have to do.
Julio, did you ever figure out how to publish to both servers with one publish?
Hi Mitch
We ended up disabling Courier as the "double publishing" quickly descended into chaos, compounded by permission issues on the load balanced servers. It's been running as a distributed simultaneous publish for a while but we'll test Courier 2 soon to see if it can deal better with load balanced environments.
is working on a reply...