wallabag is a self hostable application for saving web pages. Unlike other
services, wallabag is free (as in freedom) and open source.
With this application you will not miss content anymore. Click, save, read it
when you want. It saves the content you select so that you can read it when you
This Juju charm installs nginx and all the necessary PHP dependencies required
by the Wallabag installation.
Once the charm has installed, you may point a browser to the public IP address
of the deployed service and complete installation. Then your wallabag will be
ready to use.
The default username and password to log in to the web application is
'wallabag'/'wallabag'. Use the 'CONFIG' tab to change your password.
You really should protect your Wallabag server with TLS if you're hosting it on
public networks. For this, use a reverse proxy that supports TLS termination
such as haproxy or
apache2. In such a deployment, you may find
it more economical to place wallabag in an LXC container on the same machine.
juju deploy wallabag
juju deploy --config my-tls-conf.yaml haproxy
juju add-relation haproxy:reverseproxy wallabag
By default, wallabag uses a local sqlite database. Use a MySQL database for
better performance and scale-out:
juju deploy wallabag
juju deploy mysql
juju add-relation wallabag mysql
server_name: The public hostname of the web server.
username: and password: determine the login for the default wallabag
account upon installation. Strongly recommended if the initial deployment will be
When the wallabag charm forms a new database relation to a database that was
related to wallabag in the past, articles that were saved prior to the relation
changes will not appear in the wallabag application.
They are still stored in the database, however. The problem is that on database
reconfiguration, wallabag has assigned the user a new ID which no longer
matches the old articles.
This can usually be corrected with some UPDATE entries SET user_id = ...
SQL commands on the wallabag database.
UPDATE entries SET user_id = ...