LSCS 1 source to 2 projects ?

We want to use 1 LSCS server, and have two projects (both coming from the same TS source. One will be for Preview and the other Production.

Since the project is //server/default/main/path/to/branch I am looking for some ideas how to do this. I could probably do it with EAs but that would mean code changes.

Is it possible to change the project on deployment ? i.e., I could make //server/default/ for the Preview and //server.domain.com/default for the Production instance.

Any other options I have not thought of ? Besides add another LSCS server.

Find more posts tagged with

Comments

Adam Stoller

I don't think LSCS will allow you to stipulate the project name as distinct from the source path within TeamSite.

It might seem like extra effort but you could have either a main branch with a preview sub-branch or a main branch with a production sub-branch - such that preview and production deployments would actually come from different source locations and be distinct within LSCS.

Of course you then have to set up the branches and the workflow processes to copy the files to / from the sub-branch as desired.

nipper

Yea that is what i thought.

I wonder if I can use the lscsContext, something like

[php]

[/php]

Rick Poulin

You could, but then you'd have to basically set up a second LSCS instance on the same server. In essence, changing the context (webapp name) isn't very different from having a second LSCS instance running on a different port.

nipper

Yea I kind of figured that out.

It does look like you can defined the project name with the branchinfo statement, I am going to try that.

[php]

[/php]

JoshProx

I am not sure if that will solve the problem. If I add another branchinfo against a different project, it always picks up the first one and looks for a runtime mode defined underneath that.

nipper

Fixing post

I am not sure if that will solve the problem. If I add another branchinfo against a different project, it always picks up the first one and looks for a runtime mode defined underneath that.

[php]

[/php]

Rick Poulin

It does look like you can defined the project name with the branchinfo statement, I am going to try that.

Neat! Did that work?

nipper

Neat! Did that work?

Not yet, I can change the project name easily, but I have not been able to have 2 branch entries with the same branch, 1 for Staging and 1 for Production,

CustomCrosstabCategory.rptdesign