Skip to main content


 
@alkarex Merci, je vois qu'il y a eu un peu de changement au niveau htaccess. J'irais y jeter un œil avant de MAJ étant donné que je tourne sous nginx.

Avec nginx, il faut surtout penser à bien configurer manuellement les règles de cache HTTP, d'accès, de compression, etc., car les .htaccess fournis ne peuvent pas être utilisés. Mais rien de particulier à cette nouvelle version.

"Update system

ⓘ Your current version of FreshRSS is 1.13.0.

Last verification: January 27th 2019 at 11:43

Blast! No update to apply "

Yes, this is normal if you use the ZIP-based auto-update system, which currently requires waiting for @Marien to manually update a server. The auto-update mechanism needs to be revisited https://github.com/FreshRSS/FreshRSS/pull/1760 Meanwhile, git-based updates are more reliable.

I think I need some help, what is the best way to migrate from my current setup to a git-based setup. Which directories and configuration files should be copied to the git-clone?

The ZIP-update should now work. If you choose to move to another install system, then make a backup, and copy your data directory into the new FreshRSS folder.

So it is only the data directory, this is what I wanted to know. Thank you!

If I only copy the data directory, I am faced with the install "screen".

You can then either go through the install progress and ask to keep the current install, or manually delete the file data/do-install.txt

Done!

This means, I will be able to support with testing new releases.

Thank you!!

Great, that is welcome :-)

@alkarex Many thanks. Since the upgrade all my favicons are lost (I only see a little planet), what could cause that, and how might I solve it? Clearing some cache or something?

Vérifier les droits en écriture du serveur Web dans ./data/favicons/ (attention de bien utiliser le même utilisateur pour le cron). Pour forcer un re-téléchargement des fichiers originaux, supprimer ./data/favicons/*.ico (mais laisser les *.txt et éventuellement vérifier que le contenu contient bien une adresse valide).

@alkarex La suppression des .ico a fonctionné !