525
edits
Changes
Features/Transfer to many options (view source)
Revision as of 09:13, 13 April 2012
, 09:13, 13 April 2012no edit summary
<code>cd /etc/ssl/certs/</code>
<code>cd /etc/ssl/certs/</code>
<code>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</code></del>
<code>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</code></del>
** Configure </del>"/etc/httpd/conf.d/ssl.conf"</del> "/etc/httpd/conf/httpd.conf" to setup the WebDAV share. Sample file : [[media:httpd.conf]]
** Configure <del>"/etc/httpd/conf.d/ssl.conf"</del> "/etc/httpd/conf/httpd.conf" to setup the WebDAV share. Sample file : [[media:httpd.conf]]
*** <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.
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
** <del>Sascha's JournalToWebDAV workflow.
** Sascha's JournalToWebDAV workflow.
*** step 1
*** step 1
*** step 2
*** step 2
*** step 3
*** step 3
*** step 4</del>
*** step 4
** Alternatively,
** Alternatively,
*** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share.
*** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share.
** The popup appears, which has a new entry "Access Share" (in addition to "Make Friend").
** The popup appears, which has a new entry "Access Share" (in addition to "Make Friend").
** Clicks on "Access Share".
** Clicks on "Access Share".
** The "Browser" activity opens, with the url pointing to the "Server" buddy's webdav share.
** <del>The "Browser" activity opens, with the url pointing to the "Server" buddy's webdav share.</del>
** Thereafter, client may navigate the webdav directory hierarchy, or download files (all of which is already built in the "Browse" activity). Most importantly, there is the "Keep Link" feature in "Browse", which nicely downloads the webdav-entry, and promptly saves it in the "Journal" - something that happens in the "Send To" feature as well.
** <del>Thereafter, client may navigate the webdav directory hierarchy, or download files (all of which is already built in the "Browse" activity). Most importantly, there is the "Keep Link" feature in "Browse", which nicely downloads the webdav-entry, and promptly saves it in the "Journal" - something that happens in the "Send To" feature as well.</del>
** The server's share is mounted. A color-specific buddy-icon in the bottom tray signifies it. Clicking this icon displays the server's share's entries, on the lines of Journal/Documents/Shares/Mounted-Drives.
** Now, the entries can be copied from the mounted folder, to Journal/Documents/Shares/Mounted-Drives.
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist it in the "BaseBuddyModel" in "jarabe/model/buddy.py".
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist it in the "BaseBuddyModel" in "jarabe/model/buddy.py".
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
** Opening up the server's webdav
** <del>Opening up the server's webdav</del>
*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
*** <del>The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.</del>
** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html. (For resolving this, some additional code may have to be written, but that is something perfectly doable. However, currently awaiting a reply, to see if the code for this already exists :-) ).
** <del>A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html. (For resolving this, some additional code may have to be written, but that is something perfectly doable. However, currently awaiting a reply, to see if the code for this already exists :-) ).</del>
=== CLIENT enters the SERVER username and password in the opened "Browse" instance. ===
=== CLIENT sees the buddy icon in the bottom tray, with the server's share.. ===
**[[File:S3.png]]
**[[File:S12.png]]
=== CLIENT sees nothing shared as the SERVER has not shared anything yet. ===
=== CLIENT can copy the entries to Journal/Documents/Shares/Mounted-Drives. ===
**[[File:S4.png]]
** <to be attached>