[daisy] daisy 2.0 installation notes

[Bruno Dumon]

Hi,

Thanks for the feedback, see the inline comments...

On Fri, 2007-05-11 at 15:44 +0200, Wim Van Acker wrote:
> Hi,
> 
> Let me share some notes & thoughts about the installation of 2.0 and
> upgrade from 1.5. In general : went good, fine result, used the Tanuki 
> service scripts to start and stop Daisy.
> 
> Many thanks to the developers & the community.
> 
> In the upgrade process I noticed some things. Hopefully not already on
> the list (have done a quick search).
> 
> 1)
> 
> I think that the upgrade instructions (1.5 to 2.0) don't mention the
> addition of some new image configuration tags in myconfig.xml like :
> 
>         <!-- Should images be rotated automatically based on exif
> metadata? -->
>         <automaticRotationEnabled>true</automaticRotationEnabled>
>         <!-- Quality setting for generated jpeg's (the thumbnails and
> the original image in case of exif-based image rotation).
>              The value should be a float between 0 (lowest quality) and
> 1 (best quality). -->
>         <jpegQuality>.85</jpegQuality>
> 

Those are optional configurations, that's why the upgrade instructions
don't mention them. There's more configurations (for other components)
that are not in the default myconfig.xml

> 2)
> 
> With respect to the file daisy.xconf file, it seems that the value of
> the attributes of the tag <cacheUser> has changed between 1.5 and 2.0
> but it isn't mentioned in the upgrade instructions.
> 
> Browsing in the svn repository I find the cacheUser element in revision
> 2934 of the file daisy.xconf (in BRANCH_1_5_X) is looking as the
> following : <cacheUser login="internal" password="defaultpwd"/>.
> 
> But in the trunk repository I find that the attributes of the cacheUser
> element have changed to "guest" ... via a diff between version 2893 and
> 3111. Could it be that the upgrade instruction missed this one because
> of the branching? I suppose it should be guest? In my 1.5.1 installation
> the cacheUser was still "internal".
> 

The cache user can be whatever user you prefer. The cache user doesn't
need access to any documents (so no special ACL settings required).

In the past, it was required that this user had Administrator privileges
(and therefore the 'internal' user was reused), however the cause of
this constraint has been removed since this was limitting the
applicability of the remote Java API implementation.

> 3)
> 
> In the upgrade instructions one is asked to create a workflow user in
> the 1.5 system and remember the user/password. Later on one should enter
> the correct password in the myconfig.xml file in the workflowUser tag.
> However, I was in the impression that passwords were encrypted so how do
> I get the encrypted version of my plain-text password?

The passwords are not encrypted.

The workflow extension component needs to read this password from the
configuration in order to be able to log in to the repository.

If it were encrypted in some way, there would be yet another place were
the encryption key is read from.

The confusion might come from the complex-looking passwords in the
myconfig.xml (e.g. for the internal user), but this is simply because
those passwords are random-generated.

> 
> 4)
> 
> Because of the above remark I wandered what would happen if I changed
> the password of the workflow user via the Daisy administration pages. Of
> course being logged in as another administrator. Would the password in
> the myconfig.xml also be changed? Well ... don't think so, because my
> repository won't start anymore ... good thing I made a quick backup just
> before that.

The myconfig.xml indeed needs manual updating in that case.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno at outerthought.org                          bruno at apache.org