]> git.p6c8.net - jirafeau_project.git/blob - README.md
Merge branch 'new-screenshots' into 'next-release'
[jirafeau_project.git] / README.md
1 # Jirafeau
2
3 ![Made With](https://img.shields.io/badge/made_with-php-blue.svg)
4 ![License](https://img.shields.io/badge/license-agpl--3.0-blue.svg)
5
6 Welcome to the official Jirafeau project, an [Open-Source software](https://en.wikipedia.org/wiki/Open-source_software).
7
8 Jirafeau is a "one-click-filesharing": Select your file, upload, share a link. That's it.
9
10 See [jirafeau.net](https://jirafeau.net/) for a demo.
11
12 ![Screenshot1](screenshots/upload1.png)
13
14 ## DISCLAMER
15
16 This project is a fork of the [discontinued project](https://gitlab.com/mojo42/Jirafeau/) by [Jérôme Jutteau](https://gitlab.com/mojo42/).
17
18 If you've also forked the original project, feel free to mention it in [comments](https://gitlab.com/mojo42/Jirafeau/-/issues/360). Jérôme will add it there.
19
20 In this repository we are aiming to continue development of the original Jirafeau project. Feel free to contribute to this fork by participating in discussions and providing merge requests, so we can build the best version of Jirafeau together!
21
22 ## Main features
23
24 - One upload → one download link and one delete link
25 - Send any large files (thanks to the HTML5 file API → PHP `post_max_size` limit not relevant)
26 - Shows upload progress: speed, percentage and remaining upload time
27 - Preview content in browser (if possible)
28 - Optional password protection (for uploading or downloading)
29 - Option to require, check or generate file download passwords
30 - Set expiration time for downloads
31 - Option to self-destruct after first download
32 - Shortened URLs using Base64 encoding
33 - Maximal upload size configurable
34 - No database, only use basic PHP
35 - Simple language support with a lot of languages
36 - File level [deduplication](http://en.wikipedia.org/wiki/Data_deduplication) for storage optimization (does store duplicate files only once, but generate multiple links)
37 - Optional data encryption
38 - Small administration interface
39 - CLI script to remove expired files automatically with a cronjob
40 - Basic, adaptable "Terms Of Service" page
41 - Basic API
42 - Bash script to upload files via command line
43 - Themes
44
45 Jirafeau is a fork of the original project [Jyraphe](https://web.archive.org/web/20170506133242/home.gna.org/jyraphe) based on the 0.5 (stable version) with a **lot** of modifications.
46
47 As it's original project, Jirafeau is made in the [KISS](http://en.wikipedia.org/wiki/KISS_principle) way (Keep It Simple, Stupid).
48
49 Jirafeau project won't evolve to a file manager and will focus to keep a very few dependencies.
50
51 ## Screenshots
52
53 - [Installation - Step 1](screenshots/install1.png)
54 - [Installation - Step 2](screenshots/install2.png)
55 - [Installation - Step 3](screenshots/install3.png)
56 - [Upload - Step 1](screenshots/upload1.png)
57 - [Upload - Step 2](screenshots/upload2.png)
58 - [Upload - Progress](screenshots/upload_progress.png)
59 - [Upload - Confirmation page](screenshots/upload_confirm.png)
60 - [Admin Interface](screenshots/admin.png)
61
62 ## Installation
63
64 This shows how to install Jirafeau by your own, it's quite simple but you can
65 also use a [docker image](https://gitlab.com/jirafeau/Jirafeau/container_registry/) or build
66 it yourself. Check [docker folder](docker/README.md) for more informations.
67
68 System requirements:
69 - PHP >= 7.4
70 - Optional, but recommended: Git >= 2.7
71 - No database required, no mail required
72
73 Installation steps:
74 - Clone the [repository](https://gitlab.com/jirafeau/Jirafeau/) or download the latest [release](https://gitlab.com/jirafeau/Jirafeau/tags) from GitLab onto your webserver
75 - Set owner & group according to your webserver
76 - A) Setup with the installation wizard (web):
77 - Open your browser and go to your installed location, eg. `https://example.com/jirafeau/`
78 - The script will redirect to you to a minimal installation wizard to set up all required options
79 - All optional parameters may be set in `lib/config.local.php`, take a look at `lib/config.original.php` to see all default values
80 - B) Setup without the installation wizard (cli):
81 - Just copy `lib/config.original.php` to `lib/config.local.php` and customize it
82
83 💡 Hint: How to
84 [install & configure Jirafeau](https://www.howtoforge.com/how-to-setup-a-file-sharing-website-with-jirafeau-on-debian-10/)
85 on Debian 10 from scratch, with nginx and PHP-FPM.
86
87 ### Troubleshooting
88
89 If you have some troubles, consider the following cases
90
91 - Check your `/lib/config.local.php` file and compare it with `/lib/config.original.php`, the configuration syntax or a parameter may have changed
92 - Check owner and permissions of your files
93 - set `debug` option to `true` to check any warning or error
94
95 ## Security
96
97 `var` directory contains all files and links. It is randomly named to limit access but you may add better protection to prevent un-authorized access to it.
98 You have several options:
99 - Configure a `.htaccess`
100 - Move var folder to a place on your server which can't be directly accessed
101 - Disable automatic listing on your web server config or place a index.html in var's sub-directory (this is a limited solution)
102
103 If you are using Apache, you can add the following lines to your configuration to prevent people to access to your `var` folder:
104
105 ```apache
106 <LocationMatch "^/var-*">
107 Require all denied
108 </LocationMatch>
109 ```
110
111 Or you can put a `.htaccess` file containing this into your `var` folder:
112
113 ```apache
114 Require all denied
115 ```
116
117 If you are using nginx, you can add the following to your $vhost.conf:
118
119 ```nginx
120 location ~ /var-.* {
121 deny all;
122 return 404;
123 }
124 ```
125
126 If you are using lighttpd, you can deny access to `var` folder in your configuration:
127
128 ```
129 $HTTP["url"] =~ "^/var-*" {
130 url.access-deny = ("")
131 }
132 ```
133
134 You should also remove un-necessessary write access once the installation is done (ex: configuration file).
135 An other obvious basic security is to let access users to the site by HTTPS (make sure `web_root` in you `config.local.php` is set with https).
136
137 ## Server side encryption
138
139 Data encryption can be activated in options. This feature makes the server encrypt data and send the decrypt key to the user (inside download URL).
140 The decrypt key is not stored on the server so if you lose the download URL, you won't be able to retrieve file content.
141 Encryption is configured to use [XChaCha20-Poly1305](https://en.wikipedia.org/wiki/ChaCha20-Poly1305).
142 In case of security troubles on the server, attacker won't be able to access files.
143
144 By activating this feature, you have to be aware of few things:
145 - Data encryption has a cost (CPU) and it takes more time for downloads to complete once file sent.
146 - During the download, the server will decrypt on the fly (and use resource).
147 - This feature needs to have the [`Sodium`](https://www.php.net/manual/en/book.sodium.php) PHP module.
148 - File de-duplication will stop to work (as we can't compare two encrypted files).
149 - Be sure your server does not log client's requests.
150 - Don't forget to enable HTTPS.
151
152 In a next step, encryption will be made by the client (in JavaScript).
153
154 ## License
155
156 GNU Affero General Public License v3 (AGPL-3.0).
157
158 The GNU Affero General Public License can be found at https://www.gnu.org/licenses/agpl.html.
159
160 Please note: If you decide do make adaptions to the source code and run a service with these changes incorporated,
161 you are required to provide a link to the source code of your version in order to obey the AGPL-3.0 license.
162 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.
163 Take a look at the FAQ to find out about how to change the ToS.
164
165 PS: If you have fixed errors or added features, then please contribute to the project and send a merge request with these changes.
166
167 ## Contribution
168
169 If you want to contribute to project, then take a look at the git repository:
170
171 - https://gitlab.com/jirafeau/Jirafeau
172
173 and the Contribution Guidelines
174
175 - https://gitlab.com/jirafeau/Jirafeau/blob/master/CONTRIBUTING.md
176
177 ## FAQ
178
179 ### Can I add a new language in Jirafeau?
180
181 Of course! The best way is to create a new JSON file under `lib/locales` and open a merge request.
182
183 Thanks to all contributors ! :)
184
185 ### How do I upgrade my Jirafeau?
186
187 See change log and upgrade procedure in [CHANGELOG.md](https://gitlab.com/jirafeau/Jirafeau/blob/master/CHANGELOG.md).
188
189 ### How can I limit upload access?
190
191 There are two ways to limit upload access (but not download):
192 - you can set one or more passwords in order to access the upload interface, or/and
193 - 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
194
195 Check documentation of `upload_password` and `upload_ip` parameters in [lib/config.original.php](https://gitlab.com/jirafeau/Jirafeau/blob/master/lib/config.original.php).
196
197 ### How can I automatize the cleaning of old (expired) files?
198
199 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`.
200
201 Then the command can be placed in a cron file to automatize the process. For example:
202 ```
203 # m h dom mon dow user command
204 12 3 * * * www-data php /path/to/jirafeau/admin.php clean_expired
205 16 3 * * * www-data php /path/to/jirafeau/admin.php clean_async
206 ```
207
208 ### I have some troubles with IE
209
210 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).
211
212 Anyway I would recommend you to use another web browser. :)
213
214 ### How can I change the theme?
215
216 You may change the default theme to any of the existing ones or a custom.
217
218 Open your `lib/config.local.php` and change setting in the `style` key to the name of any folder in the `/media` directory. If you want to change the theme for dark mode, you have to set the `dark_style` key in the config file.
219
220 Hint: To create a custom theme just copy the `courgette` folder and name your theme `custom` (this way it will be ignored by git and not overwritten during updates). If you want to create a custom theme for dark mode, you have to put it in a folder named `dark-custom`. You are invited to enhance the existing themes and send pull requests however.
221
222 ### I found a bug, what should I do?
223
224 Feel free to open a bug in the [GitLab's issues](https://gitlab.com/jirafeau/Jirafeau/issues).
225 If you can, please copy-paste informations related to bug opening provided in admin interface.
226 Admin interface can be reached by accessing `/admin.php`.
227
228 ### How to set maximum file size?
229
230 If your browser supports the HTML5 file API, you can send files as big as you want.
231
232 For browsers not supporting the HTML5 file API, the limitation comes from PHP configuration.
233 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. Note that nginx setups may requiere to configure `client_max_body_size`.
234
235 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)
236
237 ### How can I edit an option?
238
239 Documentation of all default options are located in [lib/config.original.php](https://gitlab.com/jirafeau/Jirafeau/blob/master/lib/config.original.php).
240 If you want to change an option, just edit your `lib/config.local.php`.
241
242 ### How can I change the Terms of Service?
243
244 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)".
245
246 To change this text simply copy the file [/lib/tos.original.txt](https://gitlab.com/jirafeau/Jirafeau/blob/master/lib/tos.original.txt), rename it to `/lib/tos.local.txt` and adapt it to your own needs.
247
248 If you update the installation, then only the `tos.original.txt` file may change eventually, not your `tos.local.txt` file.
249
250 ### How can I access the admin interface?
251
252 Just go to `/admin.php`.
253
254 ### How can I use the scripting interface (API)?
255
256 Simply go to `/script.php` with your web browser.
257
258 ### My downloads are incomplete or my uploads fails
259
260 Be sure your PHP installation is not using safe mode, it may cause timeouts.
261
262 If you're using nginx, you might need to increase `client_max_body_size` or remove the restriction altogether. In your `nginx.conf`:
263
264 ```nginx
265 http {
266 # disable max upload size
267 client_max_body_size 0;
268 # add timeouts for very large uploads
269 client_header_timeout 30m;
270 client_body_timeout 30m;
271 }
272 ```
273
274 ### How can I monitor the use of my Jirafeau instance?
275
276 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).
277
278 ### Why forking?
279
280 In this repository we are aiming to continue development of the original Jirafeau project. We plan to add more features and increase security from a stable version.
281
282 ### What can we expect in the future?
283
284 Check [issues](https://gitlab.com/jirafeau/Jirafeau/issues) to check open bugs and incoming new stuff. :)
285
286 ### What about this file deduplication thing?
287
288 Jirafeau can use a very simple file level deduplication for storage optimization.
289
290 This means that if some people upload the same file several times, the file will only be stored once and a counter will be incremented.
291
292 If someone use his/her delete link or an admin cleans expired links, this will decrement the counter corresponding to the file.
293
294 When the counter falls to zero, the file is destroyed.
295
296 In order to know if a newly uploaded file already exist, Jirafeau will hash the file using MD5 by default but other methods are available (see `file_hash` documentation in `lib/config.original.php`).
297
298 This feature is disabled by default and can be enabled through the `file_hash` option.
299
300 ### What is the difference between "delete link" and "delete file and links" in admin interface?
301
302 When file deduplication feature is enabled, files with the same hash are not duplicated and a reference counter stores the number of links pointing to a single file.
303 So:
304 - The button "delete link" will delete the reference to the file but might not destroy the file.
305 - The button "delete file and links" will delete all references pointing to the file and will destroy the file.
306
307 ### How to contact someone from Jirafeau?
308
309 Feel free to create an [issue](https://gitlab.com/jirafeau/Jirafeau/-/issues) if you found a bug.
310
311 ### Can I buy you a coffee?
312
313 You can [drop few bucks for Jérôme Jutteau](https://www.paypal.com/paypalme/jeromejutteau)
314
315 Many Thanks <3

patrick-canterino.de