Reviewing the latest linuxserver/freshrss instructions from linuxserver/freshrss
and I see the deployment instructions have changed (and now differ from the freshrss/freshrss image instructions).
ONLY FOR NEW INSTALLS
. Don't change Volume settings for an existing container.
Where before it was
|system > docker > freshrss > data||/config/www/freshrss/data|
|system > docker > freshrss > extensions||/config/www/freshrss/extensions|
Now it should be
|system > docker > freshrss||/config|
You can also update the Environment tab with PUID and PGID so the files are mapped to a NAS user's uid and gid (get these from the SSH command line using
FOR EXISTING INSTALLATIONS
|PUID||e.g. 1026 (first user you created on DMS?)|
|PGID||e.g. 100 (users)|
. A few steps to move to the new 'all-in-one' NAS folder.
I'm going to say it's better to keep the current NAS data and extensions folders untouched (for posterity, and rollback-ability). So create a new NAS folder to hold the complete /config data: I'll call mine 'freshrss_ls
' for Linuxserver image. We're going to build a new set of /config files and copy across the current .../data and .../extensions folders.
Stop the FreshRSS container and remap the Volumes so that there is now just one defined.
|system > docker > freshrss_ls||/config|
You can also add the Environment variables too.
|PUID||e.g. 1026 (think this is the first user you created on DMS?)|
|PGID||e.g. 100 (users)|
Select the unrunning container and perform the Clear action: it resets the container and forces the GUI settings to be reapplied [and took me a few tries to realise this was needed before logins worked].
Restart the FreshRSS container and check its web page is at the setup page. Now stop the container: you've added the baseline /config files into NAS freshrss_ls
So far, so new. Now let's get your actual FreshRSS container data back into circulation...
Within File Station go to freshrss_ls/www/freshrss/
and delete the baseline data
folders (or rename them). !! make sure you're doing this in the new baseline freshrss_ls
The next step is to continue with File Station and copy
your FreshRSS folders freshrss/data/
Now restart the FreshRSS container and browsing should go to the login page ... and you can log in.
A new feature, due to /config being saved in the NAS folder, is changes to /config/crontab/root is now preserved during image updates. I prefer to set FreshRSS to perform 5 minute schedule instead of the default 15. So far I have to change this every update.