]>
Commit | Line | Data |
---|---|---|
1 | Backup wallabag | |
2 | =============== | |
3 | ||
4 | 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. | |
5 | This articles describes what you need to backup. | |
6 | ||
7 | Basic settings | |
8 | -------------- | |
9 | wallabag stores some basic parameters (like SMTP server or database backend) in the file `app/config/parameters.yml`. | |
10 | ||
11 | Database | |
12 | -------- | |
13 | 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. | |
14 | ||
15 | Here's some examples: | |
16 | ||
17 | - MySQL: http://dev.mysql.com/doc/refman/5.7/en/backup-methods.html | |
18 | - PostgreSQL: https://www.postgresql.org/docs/current/static/backup.html | |
19 | ||
20 | SQLite | |
21 | ~~~~~~ | |
22 | To backup the SQLite database, you just need to copy the directory `data/db` from the wallabag application directory. | |
23 | ||
24 | Images | |
25 | ------ | |
26 | The images retrieved by wallabag are stored under `web/assets/images` (the images storage will be implemented in wallabag 2.2). |