thanks for the info. looks like plugin installation is more developer oriented, not really an easy administrative task. i was hoping for something like a jenkins plugin setup where it's a one click install type of thing. not really a problem.
using file system based storage (or database), and there's more than one instance of jsp wiki, say for rolling upgrades or load balancing, is there a way to notify other instances of changed content and/or index needs to be updated? On Tue, Mar 12, 2024 at 3:38 PM Juan Pablo Santos Rodríguez < juanpablo.san...@gmail.com> wrote: > Hi Alex! > > thanks for your interest in JSPWiki! :-) As for your questions: > > Are there any administrative capabilities? like pages to see how much > stuff exists in the wiki? > for the latter, that can be accomplished via plugin [#1]. IIRC, The > default set of wiki pages contains pages for page index, recent and > changes / full history and a system info page with a some more wiki > information. You can see all of them at jspwiki-wiki.apache.org, on > the left menu, inside the special pages box. Don't know if you're > looking for something else though > > Ability to preload content? backup/restore? > Pages/Attachment by default are stored on files inside a directory. > The initial page load consists on unzipping a file inside a folder, so > nothing stops you from putting there more pages. For new pages to be > picked up you should restart your jspwiki instance, so they get picked > up by the indexer. There aren't any in-built capabilities to > import/export pages or backup/restore, you have to take care of that > outside JSPWiki. Also, I've said pages are stored on disk (the page > and attachment providers), but you can provide your own > page/attachment provider implementation > > User management and permissions setup? > Please see [#2] all related to Identity management, groups, ACLs > (application-wide or per page), authentication, etc. > > I'd also add the things that I like most from JSPWiki: > * very, very easy to use and setup > * almost every moving part of JSPWiki is customisable and can be > replaced with another implementation, 3rd party or not (2 page > providers, 3 search indexers, two wiki syntaxis, plugins, filters) > * deployment options (war, portable binaries, docker images) > * comprehensive security options > > > HTH, > juan pablo > > > [#1] https://jspwiki-wiki.apache.org/Wiki.jsp?page=Category.Plugins > [#2 <https://jspwiki-wiki.apache.org/Wiki.jsp?page=Category.Plugins[#2>] > https://jspwiki-wiki.apache.org/Wiki.jsp?page=Wiki.Admin.Security > > On Tue, Mar 12, 2024 at 12:14 AM Alex O'Ree <alexo...@apache.org> wrote: > > > > I'm shopping around for a java based wiki solution. I've found xwiki and > > seems pretty capable, but i've always been a fan of asf projects so i'm > > digging deep into jspwiki. > > > > Are there any administrative capabilities? like pages to see how much > stuff > > exists in the wiki? > > Ability to preload content? backup/restore? > > User management and permissions setup? >
