[Building Sakai] Resources-within-Filesystem on Windows -- SOLVED

[will at serensoft.com]

On Wed, May 20, 2009 at 11:43 AM, will at serensoft.com <will at serensoft.com> wrote:
>> If you're planning on using a network share to host the content, then
>> mapping drives won't be an option unless you plan to log in and run
>> tomcat by hand, so you'll need to be testing using the
>> \\servername\sharename format anyway (you could share the folder from
>> the local machine and test it that way). Of course, then you'll run into
>> cross-machine authorization complexities...
>
> Yes indeedy. This is a great tip, thanks, Dave! \\off\to\see\the\wizard!

And with that, the mystery is solved. Thanks, David!


HOW TO USE BODYPATH ON WINDOWS FOR STORING SAKAI RESOURCES ON A REMOTE
FILE SERVER:

We're using the backslashes, so we have to double them -- so
sakai.property includes:
bodyPath at org.sakaiproject.content.api.ContentHostingService=\\\\10.1.1.28\\SakaiResources

Here 10.1.1.28 is the file server, and SakaiResources is the folder
that's been "shared". (We were trying the drive/folder S:\\path
paradigm, which didn't work. Requires \\\\server\\share instead.)

The Sakai startup logs include:
body path: \\10.1.1.28\SakaiResources
which is correct.

And files and folders are being created! Woo hoo!

It's always the simple stuff :)

Securing said network-share is left as an (important!) exercise for the reader.

-- 
will trillich
"Our only real economic security lies in our power to meet human
needs." -- S.Covey, the 8th Habit