Assuming your shared hosting uses Apache, yes, it should be fine out of the box.
You should double check though by trying to access some files: nothing outside /p/ should work.

Please try our rolling release branch edge. Feedback welcome

I'm happy to test edge and give feedback. Can I change the "Release channel" somewhere and run an update or do I need to reinstall everything?

@kacelnik It depends on the way you deployed / installed FreshRSS? Did you take the ZIP archive and uploaded to your shared server via SFTP, or do you have an SSH access allowing a git install?

I downloaded the zip, unzipit and then uploaded everything via SFTP. No SSH I'm afraid.

Two options then (after the usual warning of first taking a backup):

1. Download a copy of our rolling release and upload the same way than what you did last time, just overriding the existing files.
2. Or if you use Web updates (requiring that the Web server has sufficient write access), you can edit your constants.php to add a -dev suffix to your existing version number in:
   

   FreshRSS/constants.php

   Line 7 in 4461784

   const FRESHRSS_VERSION = '1.24.3';

   
   to become 1.24.3-dev, on the model of:
   

   FreshRSS/constants.php

   Line 7 in 9162403

   const FRESHRSS_VERSION = '1.25.0-dev';

   
   and then proceed with the update from the Web interface

You can just stay on the rolling release and decide at the next slow release (1.25.0) whether to continue on the rolling release or switch back to the slow releases.
Otherwise, you can lie and indicate 1.24.3 again.

Thank you for all your help!
:)

Reworked in #7008