7 wallabag is compatible with php >= 5.5
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.
26 wallabag uses PDO to connect to database, so you'll need one of:
32 and it's corresponding database server.
37 wallabag uses a big number of libraries in order to function. These libraries must be installed with a tool called Composer. You need to install it if you don't already have.
43 curl -s http://getcomposer.org/installer | php
45 You can find specific instructions here : __ https://getcomposer.org/doc/00-intro.md
47 To install wallabag itself, you must run these two commands:
51 git clone git@github.com:wallabag/wallabag.git
53 git checkout 2.0.0-beta.2
54 SYMFONY_ENV=prod composer install --no-dev -o
55 php bin/console wallabag:install --env=prod
56 php bin/console server:run --env=prod
58 To start php's build-in server and test if everything did install correctly, you can do:
62 php bin/console server:run --env=prod
64 And access wallabag at http://yourserverip:8000
69 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:
75 ServerAlias www.domain.tld
77 DocumentRoot /var/www/wallabag/web
78 <Directory /var/www/wallabag/web>
83 <IfModule mod_rewrite.c>
86 RewriteCond %{REQUEST_FILENAME} !-f
87 RewriteRule ^(.*)$ app.php [QSA,L]
91 # uncomment the following lines if you install assets as symlinks
92 # or run into problems when compiling LESS/Sass/CoffeScript assets
93 # <Directory /var/www/wallabag>
94 # Options FollowSymlinks
97 # optionally disable the RewriteEngine for the asset directories
98 # which will allow apache to simply reply with a 404 when files are
99 # not found instead of passing the request into the full symfony stack
100 <Directory /var/www/wallabag/web/bundles>
101 <IfModule mod_rewrite.c>
105 ErrorLog /var/log/apache2/wallabag_error.log
106 CustomLog /var/log/apache2/wallabag_access.log combined
109 After reloading or restarting Apache, you should now be able to access wallabag at http://domain.tld.
114 Assuming you install wallabag in the /var/www/wallabag folder, here's the recipe for wallabag :
119 server_name domain.tld www.domain.tld;
120 root /var/www/wallabag/web;
123 # try to serve file directly, fallback to app.php
124 try_files $uri /app.php$is_args$args;
126 location ~ ^/app\.php(/|$) {
127 fastcgi_pass unix:/var/run/php5-fpm.sock;
128 fastcgi_split_path_info ^(.+\.php)(/.*)$;
129 include fastcgi_params;
130 # When you are using symlinks to link the document root to the
131 # current version of your application, you should pass the real
132 # application path instead of the path to the symlink to PHP
134 # Otherwise, PHP's OPcache may not properly detect changes to
135 # your PHP files (see https://github.com/zendtech/ZendOptimizerPlus/issues/126
136 # for more information).
137 fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
138 fastcgi_param DOCUMENT_ROOT $realpath_root;
139 # Prevents URIs that include the front controller. This will 404:
140 # http://domain.tld/app.php/some-path
141 # Remove the internal directive to allow URIs like this
145 error_log /var/log/nginx/wallabag_error.log;
146 access_log /var/log/nginx/wallabag_access.log;
149 After reloading or restarting nginx, you should now be able to access wallabag at http://domain.tld.