If you are unsure what to deploy, and simply tells courier to try and deploy everything, it will go though each item and determine if it needs to deploy it. depending on network and server setup this can take time as for each item it will do:
Fetch the data from the local site
Make a hash of it
Fetch a hash from the remote site (which involves fetching all data there)
Compare the hashes
If hashes are identical, skip it.
Also, for each content there are all the dependencies where courier checks hashes on some of them as well (like doctypes to ensure that they are identical on both sites)
So if you have 2 pages that have changed, but try to deploy 1200 pages every time, courier have no idea what to pick and will just go through all of them to make sure it gets it all transferred.
Thanks per, yes spent the past couple of days using it now and have trained our moderators ready for go live.
Really looking forward to the new version being released. We have been using Sharepoint for the past 4 years and it was nice having automatic content deployment.
Not so much for a small site, but for the larger sites.
Craig, there are other considerations as well. Is your live site "hands off", or is content editing allowed? If you transfer all content every time, you will overwrite changes that were made on the live site. Just make sure you have a strictly-defined process that avoids such scenarios.
Deploying changes from staging to live site?
We currently have a website which is just about to launch with about 1500 pages.
We have 3 website coordinators who are responsible for checking and ultimately deploying content to the live site.
Currently it looks like you need to know which resource you want to deploy. If not you go to the root of the site and deploy everything.
It currently takes about 20 - 30 minutes, but the site will grow.
Am I tackling things correctly? are there better procedures with courier to speed this process up?
Hi Craig
If you are unsure what to deploy, and simply tells courier to try and deploy everything, it will go though each item and determine if it needs to deploy it. depending on network and server setup this can take time as for each item it will do:
Also, for each content there are all the dependencies where courier checks hashes on some of them as well (like doctypes to ensure that they are identical on both sites)
So if you have 2 pages that have changed, but try to deploy 1200 pages every time, courier have no idea what to pick and will just go through all of them to make sure it gets it all transferred.
Thanks per, yes spent the past couple of days using it now and have trained our moderators ready for go live.
Really looking forward to the new version being released. We have been using Sharepoint for the past 4 years and it was nice having automatic content deployment.
Not so much for a small site, but for the larger sites.
Thanks
Craig, there are other considerations as well. Is your live site "hands off", or is content editing allowed? If you transfer all content every time, you will overwrite changes that were made on the live site. Just make sure you have a strictly-defined process that avoids such scenarios.
is working on a reply...