Wallabag

Wallabag is a ‘Read it later’ service for web articles.

Preparation

Set up variables and passwords in your host_vars/YOURSERVER/main.yml and host_vars/YOURSERVER/vault.yml for the Wallabag database, Wallabag account etc

Installation

Run the role.

ansible-playbook --ask-vault-pass --limit YOURSERVER play/app/wallabag.yml

You should be able to reach Wallabag at https://wallabag.YOUR-FQDN but you’ll need to create an account before you can log in, and you may see a “500 Internal Server Error”. See below:

Manually run database migration

If you get a “500 Internal Server Error” on the first visit to Wallabag URL try running the database migration scripts:

sudo su - wallabag
podman exec container-wallabag /var/www/wallabag/bin/console doctrine:migrations:migrate --env=prod --no-interaction

This was sometimes needed when using Momod to install Wallabag 2.6.2 Docker, see: Momod Issue #27 comments.

Add the first user account to Wallabag

By default Momod creates the container with user registration disabled (don’t want the entire internet to be able to create an account) and I recommend you create the user accounts using the Wallabag CLI like so:

sudo su - wallbag
podman exec container-wallabag /var/www/wallabag/bin/console fos:user:create --env=prod USERNAME EMAIL PASSWORD

You may want to have at least one user have administrator privileges. You can make your first user an admin using the --super-admin flag or create a separate admin account:

sudo su - wallabag
podman exec container-wallabag /var/www/wallabag/bin/console fos:user:create --env=prod --super-admin admin EMAIL PASSWORD

See the Wallabag documentation for more console commands.

Enable Wallabag on Momod Dashboard

This is optional, if you want the Wallabag link to work on Momod Dashboard set the app_wallabag variable in your host_vars to ’enabled’:

app_wallabag: "enabled"

And run the homer play:

ansible-playbook --limit YOURSERVER play/app/homer.yml