Changes

From SME Server
Jump to navigationJump to search
1,231 bytes added ,  12:11, 23 October 2013
m
no edit summary
Line 51: Line 51:  
=== Additional options ===
 
=== Additional options ===
   −
Some settings are available from the DB
+
Some settings are available from the DB, in the pydio entry
    
* '''Authentication''': Control the way users are authenticated. Correct values are '''http''' (apache protects the access, users need to login with their own credentials), or '''LemonLDAP''' which uses [[LemonLDAP-NG]] to grant access to the application
 
* '''Authentication''': Control the way users are authenticated. Correct values are '''http''' (apache protects the access, users need to login with their own credentials), or '''LemonLDAP''' which uses [[LemonLDAP-NG]] to grant access to the application
Line 62: Line 62:  
* '''PublicShares''': can be enabled or disabled (default is enabled). Control if users can share individual files publicly (with or without a password)
 
* '''PublicShares''': can be enabled or disabled (default is enabled). Control if users can share individual files publicly (with or without a password)
 
* '''Metastore''': can be serial or xattr (default is serial): control the way metedata are stored. With serial, metadata are stored in PHP serialized files in /var/lib/pydio/plugins/metastore.serial/. It'll always work, but the problem is that if you move or rename a file through samba, the metadata will be lost (because Pydio can't notice this). This won't happen if you set this to xattr, because metadata will be stored on the filesystem, using extended user xattr. For this to work, you have to mount your filesystem where shared folders are stored with the user_xattr option
 
* '''Metastore''': can be serial or xattr (default is serial): control the way metedata are stored. With serial, metadata are stored in PHP serialized files in /var/lib/pydio/plugins/metastore.serial/. It'll always work, but the problem is that if you move or rename a file through samba, the metadata will be lost (because Pydio can't notice this). This won't happen if you set this to xattr, because metadata will be stored on the filesystem, using extended user xattr. For this to work, you have to mount your filesystem where shared folders are stored with the user_xattr option
 +
* '''Indexer''': can be enabled or disabled (default is enabled): control the indexer process globally. If disabled, no share will be indexed. This can also be set on a per share basis
    
example:
 
example:
 
  db configuration setprop pydio access public Title 'My own web based file manager' WelcomMessage 'Powered by SME Server' DefaultLanguage fr MaxUploadSize 500M
 
  db configuration setprop pydio access public Title 'My own web based file manager' WelcomMessage 'Powered by SME Server' DefaultLanguage fr MaxUploadSize 500M
 
  signal-event webapps-update
 
  signal-event webapps-update
 +
 +
Some settings are also available on a per shared folder basis:
 +
* '''PydioIndexer''': can be enabled or disabled (default is enabled): control if the content of this share will be indexed each night by Pydio (so you can then search for key word, Pydio will provide very fast result and can also index some file content). The indexation can be resource intensive, so if you're not interested, you can disabled it for a few share
 +
* '''PydioHistory''': can be enabled or disabled (default is disabled), this should only be turned on on a newly created share. If enabled, git will be used on the shared folder to track each modification. Each revision will be browseable, and you can revert every change you want. If you enable this, you should not enable other access to this shared folder (samba or webdav) as only access through Pydio will handle commits on file modification. You should also be aware that GIT is not very scalable for huge file. For example, you shouldn't enable this option if you store big multimedia files
    
=== Integration with LemonLDAP::NG ===
 
=== Integration with LemonLDAP::NG ===

Navigation menu