PageRenderTime 26ms CodeModel.GetById 17ms RepoModel.GetById 1ms app.codeStats 0ms

/README.md

https://gitlab.com/Sondages.Pro/Jirafeau
Markdown | 275 lines | 187 code | 88 blank | 0 comment | 0 complexity | b8f9a175d053fe5cc2dffe765eaa1123 MD5 | raw file
  1. # Introduction
  2. Welcome to the official Jirafeau project, an [Open-Source software](https://en.wikipedia.org/wiki/Open-source_software).
  3. Jirafeau is a web site permitting to upload a file in a simple way and give an unique link to it.
  4. A demonstration of the latest version is available on [jirafeau.net](http://jirafeau.net/)
  5. ![Screenshot1](http://i.imgur.com/TPjh48P.png)
  6. **Main features**:
  7. - One upload => One download link & One delete linkp
  8. - Send any large files (thanks to HTML5)
  9. - NO database, only use basic PHP
  10. - Shows progression: speed, percentage and remaining upload time
  11. - Preview content in browser (if possible)
  12. - Optional Password protection (for uploading or downloading)
  13. - Time limitation
  14. - Option to self-destruct after reading
  15. - Simple language support :gb: :fr: :de: :it: :nl: :ro: :sk: :hu: :cn: :gr: :ru: :es:
  16. - Small administration interface
  17. - File level [Deduplication](http://en.wikipedia.org/wiki/Data_deduplication) for storage optimization
  18. - A basic Terms Of Service which can be adapted to your needs
  19. - Shortened URLs using base 64 encoding
  20. - API interface
  21. - Optional data encryption
  22. - Skins
  23. ...
  24. Jirafeau is a fork of the original project [Jyraphe](http://home.gna.org/jyraphe/) based on the 0.5 (stable version) with a **lot** of modifications.
  25. As it's original project, Jirafeau is made in the [KISS](http://en.wikipedia.org/wiki/KISS_principle) way (Keep It Simple, Stupid).
  26. Jirafeau project won't evolve to a file manager and will focus to keep a very few dependencies.
  27. # Screenshots
  28. Here are some screenshots:
  29. - [Installation part 1](http://i.imgur.com/hmpT1eN.jpg)
  30. - [Installation part 2](http://i.imgur.com/2e0UGKE.jpg)
  31. - [Installation part 3](http://i.imgur.com/ofAjLXh.jpg)
  32. - [Installation part 4](http://i.imgur.com/WXqnfqJ.jpg)
  33. - [Upload 1](http://i.imgur.com/SBmSwzJ.jpg)
  34. - [Upload 2](http://i.imgur.com/wzPkb1Z.jpg)
  35. - [Upload 3](http://i.imgur.com/i6n95kv.jpg)
  36. - [Upload 4](http://i.imgur.com/P2oS1MY.jpg)
  37. # Installation
  38. - [Download](https://gitlab.com/mojo42/Jirafeau/repository/archive.zip) the last version of Jirafeau from GitLab
  39. - Upload files on your web server
  40. - Don't forget to set owner of uploaded files if you need to
  41. - Get your web browser and go to you install location (e.g. ```http://your-web-site.org/jirafeau/```) and follow instructions
  42. - Some options are not configured from the minimal installation wizard, you may take a look at option documentation in ```lib/config.original.php``` and customize your ```lib/config.local.php```
  43. Note that ```lib/config.local.php``` is auto-generated during the installation.
  44. If you don't want to go through the installation wizard, you can just copy ```config.original.php``` to ```config.local.php``` and customize it.
  45. # Security
  46. ```var``` directory contain all files and links. It is randomly named to limit access but you may add better protection to prevent un-authorized access to it.
  47. You have several options:
  48. - Configure a ```.htaccess```
  49. - Move var folder to a place on your server which can't be directly accessed
  50. - Disable automatic listing on your web server config or place a index.html in var's sub-directory (this is a limited solution)
  51. If you are using Apache, you can add the following line to your configuration to prevent people to access to your ```var``` folder:
  52. ```RedirectMatch 301 ^/var-.* http://my.service.jirafeau ```
  53. If you are using nginx, you can add the following to your $vhost.conf:
  54. ```nginx
  55. location ~ /var-.* {
  56. deny all;
  57. return 404;
  58. }
  59. ```
  60. You should also remove un-necessessary write access once the installation is done (ex: configuration file).
  61. An other obvious basic security is to let access users to the site by HTTPS.
  62. # Few notes about server side encryption
  63. Data encryption can be activated in options. This feature makes the server encrypt data and send the decryt key to the user (inside download URL).
  64. The decrypt key is not stored on the server so if you loose an url, you won't be able to retrieve file content.
  65. In case of security troubles on the server, attacker won't be able to access files.
  66. By activating this feature, you have to be aware of few things:
  67. - Data encryption has a cost (cpu) and it takes more time for downloads to complete once file sent.
  68. - During the download, the server will decrypt on the fly (and use resource).
  69. - This feature needs to have the mcrypt php module.
  70. - File de-duplication will stop to work (as we can't compare two encrypted files).
  71. - Be sure your server do not log client's requests.
  72. - Don't forget to enable https.
  73. In a next step, encryption will be made by the client (in javascript), see issue #10.
  74. # FAQ
  75. ### Can I add a new language in Jirafeau?
  76. Of course ! Translations are easy to make and no technical knowledge is required.
  77. Simply go to [Jirafeau's Weblate](https://hosted.weblate.org/projects/jirafeau/master/).
  78. If you want to add a new language in the list, feel free to contact us or leave a comment in ticket #9.
  79. We would like to thank all anonymous contributors on weblate. :)
  80. ### How do I upgrade my Jirafeau?
  81. If you have installed Jirafeau using git, it's pretty simple: just make a git pull and chown/chmod files who have the owner changed.
  82. If you have installed Jirafeau just by uploading files on your server, you can take the [last version](https://gitlab.com/mojo42/Jirafeau/repository/archive.zip), overwrite files and chown/chmod files if needed.
  83. After upgrading, you can compare your ```lib/config.local.php``` and ```lib/config.original.php``` to see if new configuration items are available.
  84. If you have some troubles:
  85. - It should probably come from your ```lib/config.local.php``` (configuration syntax may have changed). Just compare it with ```lib/config.original.php```
  86. - Check owner/permissions of your files.
  87. Anyway you should off-course make a backup of your current installation before doing anything. :)
  88. ### How can I limit upload access?
  89. There are two ways to limit upload access (but not download):
  90. - you can set one or more passwords in order to access the upload interface, or/and
  91. - you can configure a list of authorized IP ([CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)) which are allowed to access to the upload page
  92. Check documentation of ```upload_password``` and ```upload_ip``` parameters in [lib/config.original.php](https://gitlab.com/mojo42/Jirafeau/blob/master/lib/config.original.php).
  93. ### How can I automatize the cleaning of old (expired) files?
  94. You can call the admin.php script from the command line (CLI) with the ```clean_expired``` or ```clean_async``` commands: ```sudo -u www-data php admin.php clean_expired```.
  95. Then the command can be placed in a cron file to automatize the process. For example:
  96. ```
  97. # m h dom mon dow user command
  98. 12 3 * * * www-data php /path/to/jirafeau/admin.php clean_expired
  99. 16 3 * * * www-data php /path/to/jirafeau/admin.php clean_async
  100. ```
  101. ### I have some troubles with IE
  102. If you have some strange behavior with IE, you may configure [compatibility mode](http://feedback.dominknow.com/knowledgebase/articles/159097-internet-explorer-ie8-ie9-ie10-and-ie11-compat).
  103. Anyway I would recommend you to use another web browser. :)
  104. ### I found a bug, what should I do?
  105. Feel free to open a bug in the [GitLab's issues](https://gitlab.com/mojo42/Jirafeau/issues).
  106. ### How to set maximum file size?
  107. If your browser supports HTML5 file API, you can send files as big as you want.
  108. For browsers who does not support HTML5 file API, the limitation come from PHP configuration.
  109. You have to set [post_max_size](https://php.net/manual/en/ini.core.php#ini.post-max-size) and [upload_max_filesize](https://php.net/manual/en/ini.core.php#ini.upload-max-filesize) in your php configuration.
  110. If you don't want to allow unlimited upload size, you can still setup a maximal file size in Jirafeau's setting (see ```maximal_upload_size``` in your configuration)
  111. ### How can I edit an option?
  112. Documentation of all default options are located in [lib/config.original.php](https://gitlab.com/mojo42/Jirafeau/blob/master/lib/config.original.php).
  113. If you want to change an option, just edit your ```lib/config.local.php```.
  114. ### How can I access the admin interface?
  115. Just go to ```/admin.php```.
  116. ### How can I use the scripting interface (API)?
  117. Simply go to ```/script.php``` with your web browser.
  118. ### My downloads are incomplete or my uploads fails
  119. Be sure your PHP installation is not using safe mode, it may cause timeouts.
  120. If you're using nginx, you might need to increase `client_max_body_size` or remove the restriction altogether. In your nginx.conf:
  121. ```nginx
  122. http {
  123. # disable max upload size
  124. client_max_body_size 0;
  125. # add timeouts for very large uploads
  126. client_header_timeout 30m;
  127. client_body_timeout 30m;
  128. }
  129. ```
  130. ### How can I monitor the use of my Jirafeau instance?
  131. You may use Munin and simple scripts to collect the number of files in the Jirafeau instance as well as the disk space occupied by all the files. You can consult this [web page](https://blog.bandinelli.net/index.php?post/2016/05/15/Scripts-Munin-pour-Jirafeau).
  132. ### Why forking?
  133. The original project seems not to be continued anymore and I prefer to add more features and increase security from a stable version.
  134. ### What can we expect in the future?
  135. Check [issues](https://gitlab.com/mojo42/Jirafeau/issues) to check open bugs and incoming new stuff. :)
  136. ### What is the Jirafeau's license?
  137. Jirafeau is licensed under [AGPLv3](https://gitlab.com/mojo42/Jirafeau/blob/master/COPYING).
  138. ### How do I modify the TOS (terms of use)?
  139. Just edit ```tos.php``` and configure ```$org``` and ```$contact``` variables.
  140. ### What about this file deduplication thing?
  141. Jirafeau uses a very simple file level deduplication for storage optimization.
  142. This mean that if some people upload several times the same file, this will only store one time the file and increment a counter.
  143. If someone use his/her delete link or an admin cleans expired links, this will decrement the counter corresponding to the file.
  144. When the counter falls to zero, the file is destroyed.
  145. ### What is the difference between "delete link" and "delete file and links" in admin interface?
  146. As explained in the previous question, files with the same md5 hash are not duplicated and a reference counter stores the number of links pointing to a single file.
  147. So:
  148. - The button "delete link" will delete the reference to the file but might not destroy the file.
  149. - The button "delete file and links" will delete all references pointing to the file and will destroy the file.
  150. ### How to contact someone from Jirafeau?
  151. Feel free to create an issue if you found a bug.
  152. # Release notes
  153. ## Version 1.0
  154. The very first version of Jirafeau after the fork of Jyraphe.
  155. - Security fix
  156. - Keep uploader's ip
  157. - Delete link for each upload
  158. - No more clear text password storage
  159. - Simple langage support
  160. - Add an admin interface
  161. - New Design
  162. - Add term of use
  163. - New path system to manage large number of files
  164. - New option to show a page at download time
  165. - Add option to activate or not preview mode
  166. ## Version 1.1
  167. - New skins
  168. - Add optional server side encryption
  169. - Unlimited file size upload using HTML5 file API
  170. - Show speed and estimated time during upload
  171. - A lot of fixes
  172. - A lot of new langages
  173. - Small API to upload files
  174. - Limit access to Jirafeau using IP, mask, passwords
  175. - Manage (some) proxy headers
  176. - Configure your maximal upload size
  177. - Configure file's lifetime durations
  178. - Preview URL
  179. - Get Jirafeau's version in admin interface
  180. ### Update from 1.0 to 1.1
  181. 1. Backup you Jirafeau installation
  182. 2. Block access to Jirafeau
  183. 3. Checkout new version using git tag 1.1
  184. 4. With you browser, go to your Jirafeau root page
  185. 5. Follow installation wizard, it should propose you the same data folder
  186. 6. Add a rewrite rule in your web server configuration to rename file.php to f.php to make old url work again
  187. 7. Go in you lib/config.local.php and lib/config.original.php to check new options and eventually change skin to 'courgette'