topic Re: Limiting customisation scope to one domain in Nuxeo Forum

Limiting customisation scope to one domain

Corinne_ — Tue, 30 Sep 2014 13:43:51 GMT

Hello all, I have 2 very different end-users groups, i'm planning to create 2 domains (one per group). Is it possible to limit the scope of some studio customisations to one domain ? How ?

Re: Limiting customisation scope to one domain

Damien_Metzler — Tue, 30 Sep 2014 14:33:38 GMT

No, it is not possible. As Studio defines for instance new document types, it's something that it configured at Nuxeo core level wich is a server wide customisation.

If the user and the customisation are different, why not use to instances of Nuxeo ?

Re: Limiting customisation scope to one domain

Corinne_ — Tue, 30 Sep 2014 15:08:44 GMT

Thank you for response. Let's go for a second nuxeo instance ! I am not very happy to have to manage an other server with postgres, tomcat, nuxeo.

Re: Limiting customisation scope to one domain

Damien_Metzler — Tue, 30 Sep 2014 15:16:25 GMT

You can use the same postgres server with jsut another DB name. And you can run the second Nuxeo instance on the same physical server which won't run on the same port. The with Apache or NGinx you configure virtual hosting so that the two nuxeo server have their own URL.

Re: Limiting customisation scope to one domain

Fred_Vadon — Tue, 30 Sep 2014 16:23:38 GMT

Depending on how much different the configuration should be on those workspace, you can also use local configuration:

http://doc.nuxeo.com/x/-I31

(Applying a Preset Look to a Space, Changing the Presentation of Document Lists, Defining the Authorized Document Types, Local Search Configurations)