]> git.p6c8.net - jirafeau_mojo42.git/blob - README.md
[FEATURE] Docs: Add system requirements
[jirafeau_mojo42.git] / README.md
1 # Jirafeau
2
3 Welcome to the official Jirafeau project, an [Open-Source software](https://en.wikipedia.org/wiki/Open-source_software).
4
5 Jirafeau is a project permitting a "one-click-filesharing", which makes it possible to upload a file in a simple way and give an unique link to it.
6
7 A demonstration of the latest version is available on [jirafeau.net](http://jirafeau.net/).
8
9 ![Screenshot1](http://i.imgur.com/TPjh48P.png)
10
11 ## Main features
12
13 - One upload → One download link & one delete link
14 - Send any large files (thanks to the HTML5 file API → PHP post_max_size limit not relevant)
15 - Shows progression: speed, percentage and remaining upload time
16 - Preview content in browser (if possible)
17 - Optional password protection (for uploading or downloading)
18 - Set expiration time for downloads
19 - Option to self-destruct after first download
20 - Shortened URLs using base 64 encoding
21 - Maximal upload size configurable
22 - NO database, only use basic PHP
23 - Simple language support :gb: :fr: :de: :it: :nl: :ro: :sk: :hu: :cn: :gr: :ru: :es:
24 - File level [Deduplication](http://en.wikipedia.org/wiki/Data_deduplication) for storage optimization (does store duplicate files only once, but generate multiple links)
25 - Optional data encryption
26 - Small administration interface
27 - CLI script to remove expired files automatically with a cronjob
28 - Basic, adaptable »Terms Of Service« page
29 - Basic API
30 - Bash script to upload files via command line
31 - Skins
32
33 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.
34
35 As it's original project, Jirafeau is made in the [KISS](http://en.wikipedia.org/wiki/KISS_principle) way (Keep It Simple, Stupid).
36
37 Jirafeau project won't evolve to a file manager and will focus to keep a very few dependencies.
38
39 ## Screenshots
40
41 - [Installation - Step 1](http://i.imgur.com/hmpT1eN.jpg)
42 - [Installation - Step 2](http://i.imgur.com/2e0UGKE.jpg)
43 - [Installation - Step 3](http://i.imgur.com/ofAjLXh.jpg)
44 - [Installation - Step 4](http://i.imgur.com/WXqnfqJ.jpg)
45 - [Upload - Step 1](http://i.imgur.com/SBmSwzJ.jpg)
46 - [Upload - Step 2](http://i.imgur.com/wzPkb1Z.jpg)
47 - [Upload - Progress](http://i.imgur.com/i6n95kv.jpg)
48 - [Upload - Confirmation page](http://i.imgur.com/P2oS1MY.jpg)
49 - [Admin Interface](http://i.imgur.com/nTdsVzn.png)
50
51 ## Installation
52
53 System requirements:
54 - PHP >= 5.6
55 - Optional, but recommended: Git >= 2.7
56 - No database required, no mail required
57
58 Installation steps:
59 - Clone the [repository](https://gitlab.com/mojo42/Jirafeau/) or download the latest ([release](https://gitlab.com/mojo42/Jirafeau/tags) from GitLab onto your webserver
60 - Set owner & group according to your webserver
61 - A) Setup with the installation wizard (web):
62 - Open your browser and go to your installed location, eg. ```https://example.com/jirafeau/```
63 - The script will redirect to you to a minimal installation wizard to set up all required options
64 - All optional parameters may be set in ```lib/config.local.php```, take a look at ```lib/config.original.php``` to see all default values
65 - B) Setup without the installation wizard (cli):
66 - Just copy ```config.original.php``` to ```config.local.php``` and customize it
67
68 ## Upgrade
69
70 ### General procedure for all versions
71
72 1. Backup your Jirafeau installation!
73 2. Block access to Jirafeau
74 3. Checkout the new version with Git using the [tagged release](https://gitlab.com/mojo42/Jirafeau/tags)
75 * If you have installed Jirafeau just by uploading files on your server, you can download the desired version, overwrite/remove all files and chown/chmod files if needed. Keep a backup of your local configuration file tough.
76 4. With you browser, go to your Jirafeau root page
77 5. Follow the installation wizard, it should propose you the same data folder or even update automatically
78 7. Check your ```/lib/config.local.php``` and compare it with the ```/lib/config.original.php``` to see if new configuration items are available
79
80 ### From version 1.0 to 1.1
81
82 1. The download URL changed
83 * Add a rewrite rule in your web server configuration to rename ```file.php``` to ```f.php``` to make older, still existing links work again
84 1. The default skin changed
85 * Optionally change the skin in ```lib/config.local.php``` to »courgette«
86
87 ### From version 1.2.0 to 2.0.0
88
89 1. The "Terms of Service" text file changed
90 * To reuse previous changes to the ToS, move the old ```/tos_text.php``` file to ```/lib/tos.local.txt``` and remove all HTML und PHP Tags, leaving a regular text file
91
92 ### Troubleshooting
93
94 If you have some troubles, consider the following cases
95
96 - Check your ```/lib/config.local.php``` file and compare it with ```/lib/config.original.php```, the configuration syntax or a parameter may have changed
97 - Check owner & permissions of your files
98
99 ## Security
100
101 ```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.
102 You have several options:
103 - Configure a ```.htaccess```
104 - Move var folder to a place on your server which can't be directly accessed
105 - Disable automatic listing on your web server config or place a index.html in var's sub-directory (this is a limited solution)
106
107 If you are using Apache, you can add the following line to your configuration to prevent people to access to your ```var``` folder:
108
109 ```RedirectMatch 301 ^/var-.* http://my.service.jirafeau ```
110
111 If you are using nginx, you can add the following to your $vhost.conf:
112
113 ```nginx
114 location ~ /var-.* {
115 deny all;
116 return 404;
117 }
118 ```
119
120 You should also remove un-necessessary write access once the installation is done (ex: configuration file).
121 An other obvious basic security is to let access users to the site by HTTPS.
122
123 ## Server side encryption
124
125 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).
126 The decrypt key is not stored on the server so if you loose an url, you won't be able to retrieve file content.
127 In case of security troubles on the server, attacker won't be able to access files.
128
129 By activating this feature, you have to be aware of few things:
130 - Data encryption has a cost (cpu) and it takes more time for downloads to complete once file sent.
131 - During the download, the server will decrypt on the fly (and use resource).
132 - This feature needs to have the mcrypt php module.
133 - File de-duplication will stop to work (as we can't compare two encrypted files).
134 - Be sure your server do not log client's requests.
135 - Don't forget to enable https.
136
137 In a next step, encryption will be made by the client (in javascript), see issue #10.
138
139 ## License
140
141 GNU Affero General Public License v3 (AGPL-3.0).
142
143 The GNU Affero General Public License can be found at https://www.gnu.org/licenses/agpl.html.
144
145 Please note: If you decide do make adaptions to the source code and run a service with these changes incorporated,
146 you are required to provide a link to the source code of your version in order to obey the AGPL-3.0 license.
147 To do so please add a link to the source (eg. a public Git repository or a download link) to the Terms of Service page.
148 Take a look at the FAQ to find out about how to change the ToS.
149
150 PS: If you have fixed errors or added features, then please contribute to the project and send a merge request with these changes.
151
152 ## Contribution
153
154 If you want to contribute to project, then take a look at the git repository:
155
156 - https://gitlab.com/mojo42/Jirafeau
157
158 and the Contribution Guidelines
159
160 - https://gitlab.com/mojo42/Jirafeau/blob/master/CONTRIBUTING.md
161
162 ## FAQ
163
164 ### Can I add a new language in Jirafeau?
165
166 Of course ! Translations are easy to make and no technical knowledge is required.
167
168 Simply go to [Jirafeau's Weblate](https://hosted.weblate.org/projects/jirafeau/master/).
169
170 If you want to add a new language in the list, feel free to contact us or leave a comment in ticket #9.
171
172 We would like to thank all anonymous contributors on weblate. :)
173
174 ### How do I upgrade my Jirafeau?
175
176 See upgrade instructions above.
177
178 ### How can I limit upload access?
179
180 There are two ways to limit upload access (but not download):
181 - you can set one or more passwords in order to access the upload interface, or/and
182 - 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
183
184 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).
185
186 ### How can I automatize the cleaning of old (expired) files?
187
188 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```.
189
190 Then the command can be placed in a cron file to automatize the process. For example:
191 ```
192 # m h dom mon dow user command
193 12 3 * * * www-data php /path/to/jirafeau/admin.php clean_expired
194 16 3 * * * www-data php /path/to/jirafeau/admin.php clean_async
195 ```
196
197 ### I have some troubles with IE
198
199 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).
200
201 Anyway I would recommend you to use another web browser. :)
202
203 ### I found a bug, what should I do?
204
205 Feel free to open a bug in the [GitLab's issues](https://gitlab.com/mojo42/Jirafeau/issues).
206
207 ### How to set maximum file size?
208
209 If your browser supports HTML5 file API, you can send files as big as you want.
210
211 For browsers who does not support HTML5 file API, the limitation come from PHP configuration.
212 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.
213
214 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)
215
216 ### How can I edit an option?
217
218 Documentation of all default options are located in [lib/config.original.php](https://gitlab.com/mojo42/Jirafeau/blob/master/lib/config.original.php).
219 If you want to change an option, just edit your ```lib/config.local.php```.
220
221 ### How can I change the Terms of Service?
222
223 The license text on the "Terms of Service" page, which is shipped with the default installation, is based on the »[Open Source Initiative Terms of Service](https://opensource.org/ToS)«.
224
225 To change this text simply copy the file [/lib/tos.original.txt](https://gitlab.com/mojo42/Jirafeau/blob/master/lib/tos.original.txt), rename it to ```/lib/tos.local.txt``` and adapt it to your own needs.
226
227 If you update the installation, then only the ```tos.original.txt``` file may change eventually, not your ```tos.local.txt``` file.
228
229 ### How can I access the admin interface?
230
231 Just go to ```/admin.php```.
232
233 ### How can I use the scripting interface (API)?
234
235 Simply go to ```/script.php``` with your web browser.
236
237 ### My downloads are incomplete or my uploads fails
238
239 Be sure your PHP installation is not using safe mode, it may cause timeouts.
240
241 If you're using nginx, you might need to increase `client_max_body_size` or remove the restriction altogether. In your nginx.conf:
242
243 ```nginx
244 http {
245 # disable max upload size
246 client_max_body_size 0;
247 # add timeouts for very large uploads
248 client_header_timeout 30m;
249 client_body_timeout 30m;
250 }
251 ```
252
253 ### How can I monitor the use of my Jirafeau instance?
254
255 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).
256
257 ### Why forking?
258
259 The original project seems not to be continued anymore and I prefer to add more features and increase security from a stable version.
260
261 ### What can we expect in the future?
262
263 Check [issues](https://gitlab.com/mojo42/Jirafeau/issues) to check open bugs and incoming new stuff. :)
264
265 ### What about this file deduplication thing?
266
267 Jirafeau uses a very simple file level deduplication for storage optimization.
268
269 This mean that if some people upload several times the same file, this will only store one time the file and increment a counter.
270
271 If someone use his/her delete link or an admin cleans expired links, this will decrement the counter corresponding to the file.
272
273 When the counter falls to zero, the file is destroyed.
274
275 ### What is the difference between "delete link" and "delete file and links" in admin interface?
276
277 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.
278 So:
279 - The button "delete link" will delete the reference to the file but might not destroy the file.
280 - The button "delete file and links" will delete all references pointing to the file and will destroy the file.
281
282 ### How to contact someone from Jirafeau?
283
284 Feel free to create an issue if you found a bug.
285
286 ## Release notes
287
288 ### Version 1.0
289
290 The very first version of Jirafeau after the fork of Jyraphe.
291
292 - Security fix
293 - Keep uploader's ip
294 - Delete link for each upload
295 - No more clear text password storage
296 - Simple langage support
297 - Add an admin interface
298 - New Design
299 - Add term of use
300 - New path system to manage large number of files
301 - New option to show a page at download time
302 - Add option to activate or not preview mode
303
304 ### Version 1.1
305
306 - New skins
307 - Add optional server side encryption
308 - Unlimited file size upload using HTML5 file API
309 - Show speed and estimated time during upload
310 - A lot of fixes
311 - A lot of new langages
312 - Small API to upload files
313 - Limit access to Jirafeau using IP, mask, passwords
314 - Manage (some) proxy headers
315 - Configure your maximal upload size
316 - Configure file's lifetime durations
317 - Preview URL
318 - Get Jirafeau's version in admin interface
319
320 ## Version 1.2.0
321
322 - Link on API page to generate bash script
323 - More informative error codes for API
324 - Security Fix: Prevent authentication bypass for admin interface
325 - CLI script to remove expired files automatically with a cronjob
326 - SHA-256 hash the admin password
327 - New theme "elegantish"
328 - Fix for JavaScript MIME-Type, prevents blocking the resource on some servers
329 - Show download link for a file in admin interface
330 - Default time for expiration (set to 'month' by default)
331 - New expiration time: 'quarter'
332 - A lof of translation contributions
333 - Code cleanups
334
335 ## Version 2.0.0
336
337 - Various documentation improvements
338 - Simplify automatic generation of local configuration file
339 - Set a custom title
340 - Bash Script: Enhanced help, show version, return link to web view as well
341 - »Terms of Service« refactored - Enable admin to overwrite the ToS, without changing existing source code → breaking, see upgrade notes

patrick-canterino.de