52020-07-19 00:26:45ClintonEbadiworkaround php not being able to write sessions in afs, guide is adequate now42020-07-18 23:40:03ClintonEbadifixed setEnvIf issue -- it wants an array of no_spaces, and no_spaces accepts "$" just fine. It's not like I implemented the action or anything and should know better...32020-07-16 04:58:30ClintonEbadiapi is also broken without fixing domtool22020-07-16 04:39:46ClintonEbadi12020-07-16 04:38:55ClintonEbadibasic install, still needs some tweaksGuide for installing and maintaining a Wallabag instance. Wallabag is a self-hosted alternative to pocket that integrates well with KOReader.

You can use either MySQL or PostgreSQL. You'll need to create a database for wallabag. The name is arbitrary but in this guide we'll be using a mysql database named wallabag (PostgreSQL support appeared to be less robust as of July 2020):

Wallabag runs from its source directory. Check the code out to wherever you want to store the webapps (except for ~/public_html). In this guide we'll be using ~/webapps/wallabag. First, checkout the source code and build the application. The Makefile will ask you several questions, the important values to set are (substitute YOU for your username, and YOUR-WALLABAG-DOMAIN for the domain you are installing wallabag on): Use http for your domain if you will not be using TLS. When the Makefile gets to the database creation step, it may ask you if you want to reset the database. Answer no and it will create the schema (answering yes just causes it to attempt to drop the database, which fails). If you need to reset the database entirely, you'll need to drop and re-create it using dbtool It will then ask if you would like to setup an admin user, you generally should. Choose an appropriate username and password, and do not use the insecure defaults.

The application will need to read the source tree, and write to ~/webapps/wallbag/var as your daemon user. Additionally, it will attempt to store session in `~/webapps/wallabag/var/sessions/prod, but PHP cannot write session files into AFS, so we symlink that to the shared sessions directory on the webserver's local filesystem. Set the appropriate openafs acls and symlinks:

This example assumes you'll be installing it as a subdomain named wallabag of another domain. Inside of the dom container for your domain:

(NB: untested)

Upstream source code Wallabag documentation Upstream installation manual Upstream upgrade guide CategoryMemberManual