You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/10/14 17:44:33 UTC

[jira] [Updated] (SLING-4050) Make it easier to run launchpad on Oak/Mongo

     [ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-4050:
---------------------------------------
    Attachment: SLING-4050.patch

Here's a patch that allows for starting the standalone launchpad (after rebuilding it of course, mvn clean install in the launchpad/builder folder) with Oak on mongo as follows:

{code}
  java -Dsling.run.modes=oak -jar target/*standalone.jar
{code}

the mongo connection string and database name are set in the org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg file, for now you need to rebuild the launchpad jar if changing them (or change the OSGi config via /system/console)

> Make it easier to run launchpad on Oak/Mongo
> --------------------------------------------
>
>                 Key: SLING-4050
>                 URL: https://issues.apache.org/jira/browse/SLING-4050
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>            Reporter: Bertrand Delacretaz
>         Attachments: SLING-4050.patch
>
>
> It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it.
> The best is probably to define two oak run modes, one for TarMK and the other for Mongo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)