mirror of https://github.com/wallabag/wallabag.git
26 lines
1016 B
ReStructuredText
26 lines
1016 B
ReStructuredText
|
Backup wallabag
|
||
|
|
===============
|
||
|
|
Because sometimes you may do a mistake with your wallabag and lose data or in case you need to move your wallabag to another server you want to backup your data.
|
||
|
|
This articles describes what you need to backup.
|
||
|
|
|
||
|
|
Basic settings
|
||
|
|
--------------
|
||
|
|
wallabag stores some basic parameters (like SMTP server or database backend) in the file `app/config/parameters.yml`.
|
||
|
|
|
||
|
|
Database
|
||
|
|
--------
|
||
|
|
As wallabag supports different kinds of database, the way to perform the backup depends on the database you use, so you need to refer to the vendor documentation.
|
||
|
|
|
||
|
|
Here's some examples:
|
||
|
|
|
||
|
|
- MySQL: http://dev.mysql.com/doc/refman/5.7/en/backup-methods.html
|
||
|
|
- PostgreSQL: https://www.postgresql.org/docs/current/static/backup.html
|
||
|
|
|
||
|
|
SQLite
|
||
|
|
~~~~~~
|
||
|
|
To backup the SQLite database, you just need to copy the directory `data/db` from the wallabag application directory.
|
||
|
|
|
||
|
|
Images
|
||
|
|
------
|
||
|
|
The images retrieved by wallabag are stored under `data/assets/images` (the images storage will be implemented in wallabag 2.2).
|