Hypothetical what if ...

SitePub
Create a Branch AAA and Sites ABC and XYZ
Publish the site to your web server which you access by http://ws.dom.com:1776/ABC/....
http://ws.dom.com:1776/XYZ/....

What if....
Create a Branch BBB and Site DEF and XYZ
Publish the site to your web server which you access by
http://ws.dom.com:1776/DEF/....

But... What happens to site XYZ?

Find more posts tagged with

Comments

interDev

SitePub
Create a Branch AAA and Sites ABC and XYZ
Publish the site to your web server which you access by http://ws.dom.com:1776/ABC/....
http://ws.dom.com:1776/XYZ/....

What if....
Create a Branch BBB and Site DEF and XYZ
Publish the site to your web server which you access by
http://ws.dom.com:1776/DEF/....

But... What happens to site XYZ?

Site XYZ content would be overwritten on webserver every time a deployment would be done from Branch AAA or Branch BBB.

You have to really see if logically this Branching strucutre makes sense or not. If 2 branches are subfolders under one domain name on webserver (which is the scenario you mentioned ), then IMO you should create one site per one branch, otherwise you can run into these kind of problems. If you have one domain pointing to one Branch, multipe sites will make sense(IMO).

new_report_3.rptdesign

Book3.xlsx

Bowker

Oh - I'm aware that that scenario is worse than evil. It's just a "what happens if." We're considering using multiple branches feeding the same LS server and mistakes do happen.

Thanks.

nipper

Oh - I'm aware that that scenario is worse than evil. It's just a "what happens if." We're considering using multiple branches feeding the same LS server and mistakes do happen.

Thanks.

Yea it is not that uncommon, I did a university that was one site per department and they had to have different branches for approvals and such.

You need a very good method to handle shared files. We got bit with having copies of the same file on each branch. XSL includes certainly help.

Crsb

Multiple branches will separate content in LSCS but of course the files in webroot will be overwritten when page has same file path. If you are querying LSCS for content by project name then you might get some separation, but you will have to specify the project name (branch name) otherwise default.site branch name will be used to query lscs.