mirror of
https://github.com/wallabag/wallabag.git
synced 2025-09-15 18:57:05 +00:00
fix path to services.yml in wallabag
parent
1693c2c093
commit
f85830d87e
1 changed files with 3 additions and 3 deletions
|
@ -24,7 +24,7 @@ cd /var/www/ftr-site-config
|
||||||
sudo git pull
|
sudo git pull
|
||||||
```
|
```
|
||||||
|
|
||||||
Now you need to inform wallabag about this second config-file folder. Within your wallabag installation path, edit the file `app/configs/services.yml` and navigate to this part:
|
Now you need to inform wallabag about this second config-file folder. Within your wallabag installation path, edit the file `app/config/services.yml` and navigate to this part:
|
||||||
|
|
||||||
```yml
|
```yml
|
||||||
Graby\SiteConfig\ConfigBuilder:
|
Graby\SiteConfig\ConfigBuilder:
|
||||||
|
@ -53,7 +53,7 @@ git pull
|
||||||
|
|
||||||
...do not need to deal with GIT themselves. You can just link the paths from FTR, which should on the same machine, of course. FTR uses two folders. Under .../standard you find the original github repo, which we later auto-update via cron job. And under .../custom the admin can write or modify his/her own config files or test it before sending them to fivefilter's repo. And as we learned previously, the site_config parameter is an array, so we can link both to wallabag 😀 The last path in the array wins. And as I want the custom folder to be highest priority, it has to be the last in the row.
|
...do not need to deal with GIT themselves. You can just link the paths from FTR, which should on the same machine, of course. FTR uses two folders. Under .../standard you find the original github repo, which we later auto-update via cron job. And under .../custom the admin can write or modify his/her own config files or test it before sending them to fivefilter's repo. And as we learned previously, the site_config parameter is an array, so we can link both to wallabag 😀 The last path in the array wins. And as I want the custom folder to be highest priority, it has to be the last in the row.
|
||||||
|
|
||||||
File `app/configs/services.yml` with content
|
File `app/config/services.yml` with content
|
||||||
```yml
|
```yml
|
||||||
Graby\SiteConfig\ConfigBuilder:
|
Graby\SiteConfig\ConfigBuilder:
|
||||||
arguments:
|
arguments:
|
||||||
|
@ -76,7 +76,7 @@ Wallabag does not use a new config immediately after it has been updated. Becaus
|
||||||
|
|
||||||
### Tip 2: Make backup of config
|
### Tip 2: Make backup of config
|
||||||
|
|
||||||
At the moment config files under `app/configs/` are not persistent. You should do a backup before upgrading your wallabag version. As service.yml will be overwritten, when upgrading wallabag, you need to restore the settings, you made above.
|
At the moment config files under `app/config/` are not persistent. You should do a backup before upgrading your wallabag version. As service.yml will be overwritten, when upgrading wallabag, you need to restore the settings, you made above.
|
||||||
|
|
||||||
### Dockerized wallabag
|
### Dockerized wallabag
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue