Skip to main content

We are a team of developers working on a Single K2 development server, all on different projects.




  • How can we make use of the Environment Library to cater for each project ?

  • Each project should have their own setting, without overwriting another setting ?

I.E : I have a Client A and Client B, both use a setting called SQL2005Connection, but they point to 2 different SQL 2005 Servers.


How do we use the Environment Library ?

Hi Eckard,


Good question and I think it seems that at the moment the only way to work around this is to create a different environment for each customer/project. This way those settings will be completely seperated. We are looking into formulating best practices for the environment library and will send that to you once it is compelte.


Cheers,


Reply