Pydio/fr
Mainteneur
Daniel B.
Firewall Services
mailto:daniel@firewall-services.com
Description
Pydio est un gestionnaire de fichiers basé sur le Web, anciennement connu sous le nom d'Ajaxplorer. Vous pouvez jeter un oeil à la démo en ligne (Utilisez "demo" en login et mot de passe). Cette contrib intègre Pydio avec la contrib SharedFolders/fr.
Si Pydio est installé, vous verrez une nouvelle option dans la configuration des dossiers partagés, vous demandant si vous souhaitez activer l'accès à ce dossier partagé par Pydio.
Requirement
Cette contrib a été développé et testé sur SME Server 8 et plus. Elle ne fonctionnera probablement pas sur SME 7 et moins.
Installation
Configurez les dépôts Firewall-Services, rpmforge et EPEL :
db yum_repositories set fws repository \ BaseURL http://repo.firewall-services.com/centos/\$releasever \ EnableGroups no GPGCheck yes \ Name "Firewall Services" \ GPGKey http://repo.firewall-services.com/RPM-GPG-KEY \ Visible yes status disabled /sbin/e-smith/db yum_repositories set rpmforge repository \ Name 'Dag - EL5' \ BaseURL 'http://apt.sw.be/redhat/el5/en/$basearch/dag' \ EnableGroups no \ GPGCheck yes \ GPGKey http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt \ Visible no \ Exclude freetype,htop,iptraf,rsync,syslinux \ status disabled db yum_repositories set epel repository \ Name 'Epel - EL5' \ BaseUrl 'http://download.fedoraproject.org/pub/epel/5/$basearch' \ MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch' \ EnableGroups no \ GPGCheck yes \ GPGKey http://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL \ Visible no \ status disabled signal-event yum-modify
- installez les RPMS
yum --enablerepo=fws --enablerepo=rpmforge --enablerepo=epel --enablerepo=smecontribs install smeserver-pydio
- Redémarrez les services services
signal-event webapps-update
Maintenant vous devez aller dans le server-manager et modifier un partage existant (ou en créer un nouveau), avec un accès Pydio autorisé. Ensuite, vous pouvez accéder à l'application à l'aide de cette URL : https://your-server.domain.tld/pydio
Chaque utilisateur ne verra que des actions auxquelles ils ont accès. Les permissions du server-manager s'appliqueront sur Pydio (comme Samba).
Options supplémentaires
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
- AliasOnPrimary: can be enabled or disabled (default is enabled). This prop lets you disable the access to Pydio on your primary domain (the alias /pydio won't be added in apache configuration). This is useful if you want the application to be available only with a virtualhost.
- access: can be public or private (default is private). Control if /pydio is available only from local networks or from the Internet.
- Title: Will be used as the title of the web page (default is Ajaxplorer)
- WelcomMessage: Can be set to a message which will be displayed while the application is loading
- DefaultLanguage: With this prop, you can set the default language for all users (you can see the list of valid languages in /usr/share/pydio/client/i18n/)
- MaxUploadSize: Restrict the file size which can be uploaded (default is 200M)
- 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
- Indexer: can be enabled or disabled (default is disabled): control the indexer process globally. If disabled, only the shares which explicitly have PydioIndexer enabled will be indexed. If enabled, all the shares, except those which have PydioIndexer disabled will be indexed.
example:
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
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 (especially if you install smeserver-ooo-headless, see below), so if you're not interested, you can disable it for a few shares.
- PydioIndexContent can be enabled or disabled, and is ignored if this share is not indexed. If enabled, the content of the files will be extracted and indexed (txt, html, PDF, even Office documents if smeserver-ooo is available). Indexing content can be time consuming. If disabled, index will only be built on the names of the files and directories.
- 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
- user's home access
If you want your users can access to their home with Pydio (only in read only mode)
db configuration setprop pydio HomeDir enabled signal-event webapps-update
Locale settings
in case of problem with your locale (XML problem) you can tweak the file /etc/pydio/bootstrap_conf.php and add your locale. By default the sme server locale is ISO-8859-1
for example this is what you need to add for French language
define("AJXP_LOCALE", "fr_FR.ISO-8859-1");
Integration with LemonLDAP::NG
Pydio can be protected by LemonLDAP::NG. Here're the steps to protect it
Disable the access on the primary domain
You should disable the access to Pydio on your primary domain:
db configuration setprop pydio AliasOnPrimary disabled signal-event webapps-update
Enable LemonLDAP::NG integration
This contrib support LemonLDAP NG auth quite easily:
db configuration setprop pydio Authentication LemonLDAP signal-event webapps-update
Create a new virtualhost for Pydio
Lets create a new virtualhost for Pydio. You can choose the name you want, for example, lets create exchange.domain.tld:
db domains set exchange.$(db configuration get DomainName) domain Content Primary Description 'Pydio' \ DocumentRoot /usr/share/pydio Nameservers internet TemplatePath WebAppVirtualHost \ LemonLDAP enabled signal-event domain-create exchange.$(db configuration get DomainName) signal-event webapps-update
Declare this virtualhost in LemonLDAP
You can now create the virtualhost in LemonLDAP management interface. You can create the rules you want. For example, here're the rules to accept only members of the group 'webexchange'
- Comment: default
- Rule: $groups =~ /\bwebexchange\b/
Office file preview and inexation
You can generate previews for office documents (doc, docx, xls, xlsx, ppt, pptx, odt, ods, odp etc...) in Pydio, and even index their content. For this to work, you need to install OpenOffice on your server in headless mode. This will install a lot of dependancies, so it's not installed automatically. If you want to add support for this, just run the below code. The DAG repository has to be available to resolve dependencies. See Dag.
yum --enablerepo=fws --enablerepo=dag install smeserver-ooo-headless signal-event webapps-update sv u /service/ooo
Uninstall
If you want to remove the contrib, just run:
yum remove pydio
Source
The source for this contrib can be found in Firewall-Services's repository [1]. You can also browse the source here