Thanks Gaincarlo -
I've spent a while going through Magnolia as much as I can so I feel a
lot more comfortable with it. My biggest interest at the minute is
getting Magnolia to start consuming data held on the file system.
Looking at repo-conf/jackrabbit-file-search.xml I noticed that the
filesystem repository is defined, although I'm not sure if it's
active. What I would like to is have Magnolia working as it is
currently, but treat a directory structure on the file system as a
data source as well. Would you be able to advise on how to do this?
Also, reading through the wiki I came cross a page on how to secure
particular pages but it seems it's extremely out of date. Do you know
how to do this in v3.5.4?
Thanks a lot for your help.
--
Regards,
Sam Gaw
Systems Administrator
Wombat Financial Software
t: +44 (0)2890 262 910
d: +44 (0)2890 262 939
m: +44 (0)781 333 1795
e: [EMAIL PROTECTED]
On 10 Feb 2008, at 17:45, Giancarlo Berner wrote:
Hi Sam
See my answers below.
Cheers
Giancarlo
On Feb 10, 2008, at 7:51 AM, Sam Gaw wrote:
I'm pretty new to Magnolia & Jackrabbit so my apologies if these
are silly questions but I was wondering if anyone could shed some
light on the following:
There are no silly questions, just silly answers ;-)
- Does Magnolia support (out-of-the-box) multiple Jackrabbit
workspaces? I'm wanting to quickly knock together a simple extranet
style site to distribute nightly builds via ACLs but because of the
sheer volume of data updated (~100GB daily) using the web interface
simply isn't an option. WebDAV had been mentioned to me before but
after reading all that I can, it seems as though the WebDAV module
is still shelved; so really having Jackrabbit watch the local file
system for updates seems the only feasible way, and the most ideal
if I'm honest. Has anyone tried anything like this before?
Yes, any JSR 170 compliant repository supports workspaces. But I
suppose you mean "multiple persistence managers". Magnolia has
multiple pre-configured persistence managers out-of-the-box. And
since Jackrabbit is the JSR 170 Reference Implementation of a JCR,
you can of course configure additional PMs.
I strongly recommend that you invest some time in the JSR 170
specification.
- In terms of DBs, have there been any deployments using Postgres
as the backend?
I have only used "MySQL" as RDBMS storage format, but there are
solutions out there running with Postgres. Maybe you want to check
out http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ which
nicely explains the PMs.
- Reading some of the recent posts on this list over documentation
this might be a bit redundant but is there anything other than the
wiki & the documentation site? When I say documentation, I'm
talking more along the lines of deployment and administration. Is
there anything that begins to explain the admin panel etc. and
making use of all the features after a fresh install or is it
simply a case of playing about to see what happens?
Yes, documentation is limited. However, there is a new initiative
going on to recuperate documentation. Most teckies though love
digging into the source code and do some "reverse engineering"
tutorial work.
Once you understand the concept, you will notice how easy and
intuitive Magnolia is. This also the point were I strongly recommend
you visiting the "Magnolia Developer Training". This comprehensive 4
day training covers most of the subjects you need to know for your
day-to-day project work. Currently a "System Administrator" and a
"Project Manager" Training are in their final stage.
In addition there are also Magnolia Partners worldwide offering
professional services
- Is anybody using any web stats/analytics applications to track
visitor usage patterns in Magnolia? I'm looking into Bizgres (http://www.bizgres.org
) to manage & report clickstream data but until I get a better idea
of how Magnolia works and get this site up & running it's probably
going to sit on my todo pile for awhile.
Have you also looked into Google Analytics? GA is very easy to
implement and generates enough reports for the general usage. You
may also want to check if AWStat meets you requirements.
But implementing HitBox or other stat tool is rather easy and
straight forward.
Please, any help or advise would be greatly appreciated,
particularly on the file system & documentation/admin guide points.
Cheers.
Regards,
Sam
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
