21 Jul
2015
21 Jul
'15
6:44 a.m.
Hi,
Is there a convenient way to install XWiki Platform without all the extra Enterprise Wiki
packages? I'm wanting to run an instance for a specific project, and I'd prefer
not to distract users with all the wiki-related elements. I'm running Ubuntu and there
only appears to be xwiki-enterprise deb package available.
Thanks,
Bryn
26 Jul
26 Jul
noon
Hi Bryn,
On 21 Jul 2015 at 07:45:59, Bryn Jeffries
(bryn.jeffries@sydney.edu.au(mailto:bryn.jeffries@sydney.edu.au)) wrote:
Hi,
Is there a convenient way to install XWiki Platform without all the extra Enterprise Wiki
packages? I'm wanting to run an instance for a specific project, and I'd prefer
not to distract users with all the wiki-related elements. I'm running Ubuntu and there
only appears to be xwiki-enterprise deb package available.
You’re referring to UI right?
One solution is to skip the Distribution Wizard at startup and then you install only the
Extensions you wish to have, using the Extension Manager in the Admin UI.
In the future, the idea is to propose flavors and to have a base flavor to make that even
easier.
Thanks
-Vincent
Thanks,
Bryn
27 Jul
27 Jul
1:33 a.m.
I wrote:
> Is there a convenient way to install XWiki
Platform without all the extra Enterprise Wiki packages? I'm wanting to run an
instance for a specific project, and I'd prefer not to distract users with all the
wiki-related elements. I'm running Ubuntu and there only appears to be
xwiki-enterprise deb package available.
Vincent replied:
You’re referring to UI right?
I guess so. The language on the XWiki website distinguishes "XWiki Platform"
from "XWiki Enterprise". I want to be able to write applications consisting of
Groovy and Velocity scripts that make use of the XWiki UI components, context and its
authentication and authorization features, and I don't necessarily want a wiki, blog,
etc.
One solution is to skip the Distribution Wizard at
startup and then you install only the Extensions you wish to have, using the Extension
Manager in the Admin UI.
Perfect, I think that's what I'm after. Thanks.
In the future, the idea is to propose flavors and to
have a base flavor to make that even easier.
A base ("Platform"?) makes sense, but I'm not sure there's a logical
need for specific flavours. Is there a great advantage over Platform + extensions? I can
see the merit of supporting "packs" of interdependent or related extensions, but
supporting multiple flavours sounds like a maintenance headache. But I'm seeing things
through my own narrow view so maybe there's a better case for this from the more
common usage patterns.
Thanks,
Bryn
3340
days inactive
3345
days old
2 comments
2 participants
participants (2)
-
Bryn Jeffries -
vincent＠massol.net