]>
Commit | Line | Data |
---|---|---|
1 | Install wallabag | |
2 | ================ | |
3 | ||
4 | Requirements | |
5 | ------------ | |
6 | ||
7 | wallabag is compatible with PHP >= 5.5, including PHP 7. | |
8 | ||
9 | .. note:: | |
10 | ||
11 | To install wallabag easily, we provide a ``Makefile``, so you need to have the ``make`` tool. | |
12 | ||
13 | wallabag uses a large number of PHP libraries in order to function. These libraries must be installed with a tool called Composer. You need to install it if you have not already done so and be sure to use the 1.2 version (if you already have Composer, run a ``composer selfupdate``). | |
14 | ||
15 | Install Composer: | |
16 | ||
17 | :: | |
18 | ||
19 | curl -s https://getcomposer.org/installer | php | |
20 | ||
21 | You can find specific instructions `here <https://getcomposer.org/doc/00-intro.md>`__. | |
22 | ||
23 | You'll also need the following extensions for wallabag to work. Some of these may already activated in your version of PHP, so you may not have to install all corresponding packages. | |
24 | ||
25 | - php-session | |
26 | - php-ctype | |
27 | - php-dom | |
28 | - php-hash | |
29 | - php-simplexml | |
30 | - php-json | |
31 | - php-gd | |
32 | - php-mbstring | |
33 | - php-xml | |
34 | - php-tidy | |
35 | - php-iconv | |
36 | - php-curl | |
37 | - php-gettext | |
38 | - php-tokenizer | |
39 | - php-bcmath | |
40 | ||
41 | wallabag uses PDO to connect to the database, so you'll need one of the following: | |
42 | ||
43 | - pdo_mysql | |
44 | - pdo_sqlite | |
45 | - pdo_pgsql | |
46 | ||
47 | and its corresponding database server. | |
48 | ||
49 | Installation | |
50 | ------------ | |
51 | ||
52 | On a dedicated web server (recommended way) | |
53 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
54 | ||
55 | To install wallabag itself, you must run the following commands: | |
56 | ||
57 | :: | |
58 | ||
59 | git clone https://github.com/wallabag/wallabag.git | |
60 | cd wallabag && make install | |
61 | ||
62 | To start PHP's build-in server and test if everything did install correctly, you can do: | |
63 | ||
64 | :: | |
65 | ||
66 | make run | |
67 | ||
68 | And access wallabag at http://yourserverip:8000 | |
69 | ||
70 | .. tip:: | |
71 | ||
72 | To define parameters with environment variables, you have to set these variables with ``SYMFONY__`` prefix. For example, ``SYMFONY__DATABASE_DRIVER``. You can have a look at `Symfony documentation <http://symfony.com/doc/current/cookbook/configuration/external_parameters.html>`__. | |
73 | ||
74 | On a shared hosting | |
75 | ~~~~~~~~~~~~~~~~~~~ | |
76 | ||
77 | We provide a package with all dependencies inside. | |
78 | The default configuration uses SQLite for the database. If you want to change these settings, please edit ``app/config/parameters.yml``. | |
79 | ||
80 | We already created a user: login and password are ``wallabag``. | |
81 | ||
82 | .. caution:: With this package, wallabag doesn't check for mandatory extensions used in the application (theses checks are made during ``composer install`` when you have a dedicated web server, see above). | |
83 | ||
84 | Execute this command to download and extract the latest package: | |
85 | ||
86 | .. code-block:: bash | |
87 | ||
88 | wget https://wllbg.org/latest-v2-package && tar xvf latest-v2-package | |
89 | ||
90 | You will find the `md5 hash of the latest package on our website <https://www.wallabag.org/pages/download-wallabag.html>`_. | |
91 | ||
92 | Now, read the following documentation to create your virtual host, then access your wallabag. | |
93 | If you changed the database configuration to use MySQL or PostgreSQL, you need to create a user via this command ``php bin/console wallabag:install --env=prod``. | |
94 | ||
95 | Installation with Docker | |
96 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
97 | ||
98 | We provide you a Docker image to install wallabag easily. Have a look at our repository on `Docker Hub <https://hub.docker.com/r/wallabag/wallabag/>`__ for more information. | |
99 | ||
100 | Command to launch container | |
101 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
102 | ||
103 | .. code-block:: bash | |
104 | ||
105 | docker pull wallabag/wallabag | |
106 | ||
107 | Virtual hosts | |
108 | ------------- | |
109 | ||
110 | Configuration on Apache | |
111 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
112 | ||
113 | Assuming you install wallabag in the ``/var/www/wallabag`` folder and that you want to use PHP as an Apache module, here's a vhost for wallabag: | |
114 | ||
115 | :: | |
116 | ||
117 | <VirtualHost *:80> | |
118 | ServerName domain.tld | |
119 | ServerAlias www.domain.tld | |
120 | ||
121 | DocumentRoot /var/www/wallabag/web | |
122 | <Directory /var/www/wallabag/web> | |
123 | AllowOverride None | |
124 | Order Allow,Deny | |
125 | Allow from All | |
126 | ||
127 | <IfModule mod_rewrite.c> | |
128 | Options -MultiViews | |
129 | RewriteEngine On | |
130 | RewriteCond %{REQUEST_FILENAME} !-f | |
131 | RewriteRule ^(.*)$ app.php [QSA,L] | |
132 | </IfModule> | |
133 | </Directory> | |
134 | ||
135 | # uncomment the following lines if you install assets as symlinks | |
136 | # or run into problems when compiling LESS/Sass/CoffeScript assets | |
137 | # <Directory /var/www/wallabag> | |
138 | # Options FollowSymlinks | |
139 | # </Directory> | |
140 | ||
141 | # optionally disable the RewriteEngine for the asset directories | |
142 | # which will allow apache to simply reply with a 404 when files are | |
143 | # not found instead of passing the request into the full symfony stack | |
144 | <Directory /var/www/wallabag/web/bundles> | |
145 | <IfModule mod_rewrite.c> | |
146 | RewriteEngine Off | |
147 | </IfModule> | |
148 | </Directory> | |
149 | ErrorLog /var/log/apache2/wallabag_error.log | |
150 | CustomLog /var/log/apache2/wallabag_access.log combined | |
151 | </VirtualHost> | |
152 | ||
153 | ||
154 | .. tip:: Note for Apache 2.4, in the section `<Directory /var/www/wallabag/web>` you have to replace the directives : | |
155 | ||
156 | :: | |
157 | ||
158 | AllowOverride None | |
159 | Order Allow,Deny | |
160 | Allow from All | |
161 | ||
162 | ||
163 | by | |
164 | ||
165 | :: | |
166 | ||
167 | Require All granted | |
168 | ||
169 | ||
170 | After reloading or restarting Apache, you should now be able to access wallabag at http://domain.tld. | |
171 | ||
172 | Configuration on Nginx | |
173 | ~~~~~~~~~~~~~~~~~~~~~~ | |
174 | ||
175 | Assuming you installed wallabag in the ``/var/www/wallabag`` folder, here's the recipe for wallabag : | |
176 | ||
177 | :: | |
178 | ||
179 | server { | |
180 | server_name domain.tld www.domain.tld; | |
181 | root /var/www/wallabag/web; | |
182 | ||
183 | location / { | |
184 | # try to serve file directly, fallback to app.php | |
185 | try_files $uri /app.php$is_args$args; | |
186 | } | |
187 | location ~ ^/app\.php(/|$) { | |
188 | fastcgi_pass unix:/var/run/php5-fpm.sock; | |
189 | fastcgi_split_path_info ^(.+\.php)(/.*)$; | |
190 | include fastcgi_params; | |
191 | # When you are using symlinks to link the document root to the | |
192 | # current version of your application, you should pass the real | |
193 | # application path instead of the path to the symlink to PHP | |
194 | # FPM. | |
195 | # Otherwise, PHP's OPcache may not properly detect changes to | |
196 | # your PHP files (see https://github.com/zendtech/ZendOptimizerPlus/issues/126 | |
197 | # for more information). | |
198 | fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name; | |
199 | fastcgi_param DOCUMENT_ROOT $realpath_root; | |
200 | # Prevents URIs that include the front controller. This will 404: | |
201 | # http://domain.tld/app.php/some-path | |
202 | # Remove the internal directive to allow URIs like this | |
203 | internal; | |
204 | } | |
205 | ||
206 | # return 404 for all other php files not matching the front controller | |
207 | # this prevents access to other php files you don't want to be accessible. | |
208 | location ~ \.php$ { | |
209 | return 404; | |
210 | } | |
211 | ||
212 | error_log /var/log/nginx/wallabag_error.log; | |
213 | access_log /var/log/nginx/wallabag_access.log; | |
214 | } | |
215 | ||
216 | After reloading or restarting nginx, you should now be able to access wallabag at http://domain.tld. | |
217 | ||
218 | .. tip:: | |
219 | ||
220 | When you want to import large files into wallabag, you need to add this line in your nginx configuration ``client_max_body_size XM; # allows file uploads up to X megabytes``. | |
221 | ||
222 | Configuration on lighttpd | |
223 | ~~~~~~~~~~~~~~~~~~~~~~~~~ | |
224 | ||
225 | Assuming you install wallabag in the ``/var/www/wallabag`` folder, here's the recipe for wallabag (edit your ``lighttpd.conf`` file and paste this configuration into it): | |
226 | ||
227 | :: | |
228 | ||
229 | server.modules = ( | |
230 | "mod_fastcgi", | |
231 | "mod_access", | |
232 | "mod_alias", | |
233 | "mod_compress", | |
234 | "mod_redirect", | |
235 | "mod_rewrite", | |
236 | ) | |
237 | server.document-root = "/var/www/wallabag/web" | |
238 | server.upload-dirs = ( "/var/cache/lighttpd/uploads" ) | |
239 | server.errorlog = "/var/log/lighttpd/error.log" | |
240 | server.pid-file = "/var/run/lighttpd.pid" | |
241 | server.username = "www-data" | |
242 | server.groupname = "www-data" | |
243 | server.port = 80 | |
244 | server.follow-symlink = "enable" | |
245 | index-file.names = ( "index.php", "index.html", "index.lighttpd.html") | |
246 | url.access-deny = ( "~", ".inc" ) | |
247 | static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" ) | |
248 | compress.cache-dir = "/var/cache/lighttpd/compress/" | |
249 | compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" ) | |
250 | include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port | |
251 | include_shell "/usr/share/lighttpd/create-mime.assign.pl" | |
252 | include_shell "/usr/share/lighttpd/include-conf-enabled.pl" | |
253 | dir-listing.activate = "disable" | |
254 | ||
255 | url.rewrite-if-not-file = ( | |
256 | "^/([^?]*)(?:\?(.*))?" => "/app.php?$1&$2", | |
257 | "^/([^?]*)" => "/app.php?=$1", | |
258 | ) | |
259 | ||
260 | Rights access to the folders of the project | |
261 | ------------------------------------------- | |
262 | ||
263 | Test environment | |
264 | ~~~~~~~~~~~~~~~~ | |
265 | ||
266 | When we just want to test wallabag, we just run the command ``make run`` to start our wallabag instance and everything will go smoothly because the user who started the project can access to the current folder naturally, without any problem. | |
267 | ||
268 | Production environment | |
269 | ~~~~~~~~~~~~~~~~~~~~~~ | |
270 | ||
271 | As soon as we use Apache or Nginx to access to our wallabag instance, and not from the command ``make run`` to start it, we should take care to grant the good rights on the good folders to keep safe all the folders of the project. | |
272 | ||
273 | To do so, the folder name, known as ``DocumentRoot`` (for apache) or ``root`` (for Nginx), has to be absolutely accessible by the Apache/Nginx user. Its name is generally ``www-data``, ``apache`` or ``nobody`` (depending on linux system used). | |
274 | ||
275 | So the folder ``/var/www/wallabag/web`` has to be accessible by this last one. But this may not be enough if we just care about this folder, because we could meet a blank page or get an error 500 when trying to access to the homepage of the project. | |
276 | ||
277 | This is due to the fact that we will need to grant the same rights access on the folder ``/var/www/wallabag/var`` like those we gave on the folder ``/var/www/wallabag/web``. Thus, we fix this problem with the following command: | |
278 | ||
279 | .. code-block:: bash | |
280 | ||
281 | chown -R www-data:www-data /var/www/wallabag/var | |
282 | ||
283 | It has to be the same for the following folders | |
284 | ||
285 | * /var/www/wallabag/bin/ | |
286 | * /var/www/wallabag/app/config/ | |
287 | * /var/www/wallabag/vendor/ | |
288 | * /var/www/wallabag/data/ | |
289 | ||
290 | by entering | |
291 | ||
292 | .. code-block:: bash | |
293 | ||
294 | chown -R www-data:www-data /var/www/wallabag/bin | |
295 | chown -R www-data:www-data /var/www/wallabag/app/config | |
296 | chown -R www-data:www-data /var/www/wallabag/vendor | |
297 | chown -R www-data:www-data /var/www/wallabag/data/ | |
298 | ||
299 | otherwise, sooner or later you will see these error messages: | |
300 | ||
301 | .. code-block:: bash | |
302 | ||
303 | Unable to write to the "bin" directory. | |
304 | file_put_contents(app/config/parameters.yml): failed to open stream: Permission denied | |
305 | file_put_contents(/.../wallabag/vendor/autoload.php): failed to open stream: Permission denied | |
306 | ||
307 | Additional rules for SELinux | |
308 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
309 | ||
310 | If SELinux is enabled on your system, you will need to configure additional contexts in order for wallabag to function properly. To check if SELinux is enabled, simply enter the following: | |
311 | ||
312 | ``getenforce`` | |
313 | ||
314 | This will return ``Enforcing`` if SELinux is enabled. Creating a new context involves the following syntax: | |
315 | ||
316 | ``semanage fcontext -a -t <context type> <full path>`` | |
317 | ||
318 | For example: | |
319 | ||
320 | ``semanage fcontext -a -t httpd_sys_content_t "/var/www/wallabag(/.*)?"`` | |
321 | ||
322 | This will recursively apply the httpd_sys_content_t context to the wallabag directory and all underlying files and folders. The following rules are needed: | |
323 | ||
324 | +-----------------------------------+----------------------------+ | |
325 | | Full path | Context | | |
326 | +===================================+============================+ | |
327 | | /var/www/wallabag(/.*)? | ``httpd_sys_content_t`` | | |
328 | +-----------------------------------+----------------------------+ | |
329 | | /var/www/wallabag/data(/.*)? | ``httpd_sys_rw_content_t`` | | |
330 | +-----------------------------------+----------------------------+ | |
331 | | /var/www/wallabag/var/logs(/.*)? | ``httpd_log_t`` | | |
332 | +-----------------------------------+----------------------------+ | |
333 | | /var/www/wallabag/var/cache(/.*)? | ``httpd_cache_t`` | | |
334 | +-----------------------------------+----------------------------+ | |
335 | ||
336 | After creating these contexts, enter the following in order to apply your rules: | |
337 | ||
338 | ``restorecon -R -v /var/www/wallabag`` | |
339 | ||
340 | You can check contexts in a directory by typing ``ls -lZ`` and you can see all of your current rules with ``semanage fcontext -l -C``. | |
341 | ||
342 | If you're installing the preconfigured latest-v2-package, then an additional rule is needed during the initial setup: | |
343 | ||
344 | ``semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/wallabag/var"`` | |
345 | ||
346 | After you successfully access your wallabag and complete the initial setup, this context can be removed: | |
347 | ||
348 | :: | |
349 | ||
350 | semanage fcontext -d -t httpd_sys_rw_content_t "/var/www/wallabag/var" | |
351 | retorecon -R -v /var/www/wallabag/var |