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