I tried to edit files in the “html” docker volume and I noticed that every time ttrss-app restarts, it overwrites my changes. Please forgive me if I’m mistaken, but I believe Docker best practice is for Docker containers to respect user changes to the volumes because the purpose of volumes is to persist user changes between container instances. If ttrss overwrites the “html” volume every time it starts, what’s the point of even putting the www code inside a volume?
If you agree, it would be very helpful if the Dockerfile for ttrss-app would be edited so it would not make changes to the html volume, unless the html volume is 100% empty and is being initially created.
Details about the problem I was trying to fix:
My reverse proxy was fighting the SELF_URL_PATH enforcement and index.php redirection, and resulting in infinite redirect loops. I deleted the /index.php that redirects to /tt-rss/, and I moved the contents of /tt-rss/ to the root directory of the html volume. But the next time I started ttrss-app, the index.php was overwritten with the redirection code and all the files were back in /tt-rss/ again.
Thank you for the excellent web app and your devotion to it!