525
edits
Changes
Jump to navigation
Jump to search
Line 28:
Line 28: − + − + − − − − − * '''[Code-Requirements] Setting up WebDAV on a server XO.''' − ** "httpd" will have to be patched, so that PROPFIND also returns Sugar's metadata as properties (in obvious addition to the standard WebDAV properties [http://rfc-ref.org/RFC-TEXTS/2518/chapter13.html]) Line 46:
Line 40: − ** Sascha's JournalToWebDAV workflow.+ − *** step 1+ − *** step 2+ − *** step 3+ − *** step 4 − ** Alternatively, − *** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share. − *** "Share" would follow all the schematics of "Documents" type. After all, "Share" is just a folder in the filesystem (like "Documents"). − *** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf"). − *** All entries in the "Share" folder would be available to client XOs. − + − ** For the second alternative, "Share" listview needs to be added on the lines of "Documents" listview. Code-reuse should be done as much as possible. Ideally, there should just be a difference of the "folder-path".
Features/Transfer to many options (view source)
Revision as of 16:38, 26 April 2012
, 16:38, 26 April 2012no edit summary
*** <del>Firstly, this sets up the paths "SSLCertificateFile" and "SSLCertificateKeyFile", which are required for HTTPS over SSL.</del>
*** <del>Firstly, this sets up the paths "SSLCertificateFile" and "SSLCertificateKeyFile", which are required for HTTPS over SSL.</del>
*** <del>Secondly</del>This sets up "/var/www/web1/web" as the "webdav" folder. In other words, whetever entries are present in this folder, will be made available for the client XOs.
*** <del>Secondly</del>This sets up "/var/www/web1/web" as the "webdav" folder. In other words, whetever entries are present in this folder, will be made available for the client XOs.
** <del>Generate authentication file for the webdav folder. These user-password credentials will be asked whenever a client tries to access the webdav folder. For example, the following list of commands sets "test" as the user, and "olpc" as the password.
** Generate authentication file for the webdav folder. These user-password credentials will be asked whenever a client tries to access the webdav folder. For example, the following list of commands sets "test" as the user, and "olpc" as the password.
<code>sudo htpasswd -c /var/www/web1/passwd.dav test
<code>sudo htpasswd -c /var/www/web1/passwd.dav test
New password: <olpc>
New password: <olpc>
Re-type new password: <olpc>
Re-type new password: <olpc>
Adding password for user test</code></del>
Adding password for user test</code>
** Start service "httd".
** Start service "httd".
** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE.
** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE.
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share.
** "Share" would follow all the schematics of "Documents" type. After all, "Share" is just a folder in the filesystem (like "Documents").
** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf").
** All entries in the "Share" folder would be available to client XOs.
* '''[Code-Requirements] Exporting Data to WebDav, on a server XO.'''
* '''[Code-Requirements] Exporting Data to WebDav, on a server XO.'''
** Sascha has already coded the first alternative.
** "Share" listview needs to be added on the lines of "Documents" listview. Code-reuse should be done as much as possible. Ideally, there should just be a difference of the "folder-path".