Docker-compose + tt-rss

Why does the docker setup use the standard location /var/www/html for web files?

Not surprisingly this clashes with my nginx installation; I don’t get the point of dockerising but putting a volume in a well-known location which immediately breaks the isolation.

Am I missing something?

hint: this well known location is inside the container, mapped to a storage volume.

i have no idea how would you even make this path clash with what is presumably your host :face_with_raised_eyebrow:

Sorry I was reading it the wrong way round, doh!

Any suggestion about add Access-Control-Allow-Origin for use in api using docker?

The FAQ had a nice description of a nginx reverse proxy setup. I was able to take that and make it work with apache. Would someone be able to add this to the FAQ?

You need to run

a2enmod proxy
a2enmod proxy_http

To get apache to load the mod_proxy module. Then add a config file to /etc/apache2/sites-enabled, such as this:

<VirtualHost *:80>
    ServerName domain.com

    ProxyPreserveHost On
    ProxyRequests Off

    # Server IP + the exposed port of docker container 
    ProxyPass / http://127.0.0.1:8280/
    ProxyPassReverse / http://127.0.0.1:8280/
</VirtualHost>

I didn’t see much out here as to backing up the database. I was able to write a script with the following lines to get it working:

source .env
docker-compose exec db /bin/bash \
  -c "export PGPASSWORD=$POSTGRES_PASSWORD \
  && pg_dump -U $POSTGRES_USER $POSTGRES_USER" \
  | gzip -9 > backup.sql.gz

Would that be worth adding to the FAQ?

I haven’t tried restoring to a new machine yet, but presumably it would be a similar command.

sure, why not. i’ll add this to the wiki. thanks.

e: added to https://git.tt-rss.org/fox/ttrss-docker-compose/wiki/Home

The guide was great, thanks - one issue: created it, changed owner/user id in .env, the created index.php didn’t have global read permissions and the wrong owner so I couldn’t access the webview until I fixed that manually

Would it be possible to have the nginx configuration listen on ipv6 as well as v4? Change is very simple:

--- a/web-nginx/nginx.conf
+++ b/web-nginx/nginx.conf
@@ -22,6 +22,7 @@ http {
 
        server {
                listen 80;
+               listen [::]:80;
                root /var/www/html;
 
                location /tt-rss/cache {

Cheers

David

sure, why not. i’ll make a note to update this unless someone else does a PR first.

Hi, I’m completely unfamiliar with docker-compose. I used to have a regular tt-rss set-up and I now need a fresh install.
I’d like

  • to specify where the db is to be stored
  • to access it directly through mydomain rather than mydomain/tt-rss/

I don’t think the recommended docker set-up covers both of these things. I’ve tried to edit every /tt-rss occurrence I found, and the way the database backup in the wiki looks like hints me that it is not easy to access the db.
How can I achieve that? Is there a docker set-up that would match my expectations?

You would need to build your own.

The supplied Docker setup’s Database is in the DB container and the other containers connect to it using built in docker networking. We are not a Docker support forum to direct you on that.

Fox has said up thread he is not interested in serving at the root of the host. You would also need to heavily edit the web container. When I first switched to this it also bothered me, but I have added a few new containers and have found that with a good reverse proxy setup Fox was right. Using the subfolder makes the proxy easier to manage.

Sounds like I should rather go for a direct install till I get knowledgeable about Docker, thanks.

I’ve read everything I could (README.md and this forum), but I still have a bug that I can’t wrap my head around.

First, know that everything worked fine with the containers images back in May. I’ve upgraded to the latest containers images with a docker-compose pull && docker-compose down && docker-compose up -d and now I have this one bug: if I left click on the title/link I get redirected to http://127.0.0.1:8280/tt-rss/backend.php

Here are the steps to reproduce this bug (I’d like at least to know if I’m the only one with it):

  1. Go to “Special / All articles”
  2. Left-click on any article (it will expand it)
  3. Left-click again on the article title
  4. It opens a new tab with this URL: http://127.0.0.1:8280/tt-rss/backend.php

Strangely enough, if I use the middle-click in step 2 or 3, it opens a new tab with the correct URL (i.e. the article URL).

Do you have the same behavior?

Thank you.

the only bug here is your inability to follow simple instructions

e: me not spoonfeeding you is deliberate

I’ve got to wonder what happened in your life that made you so salty. I asked two questions in this forum, I played it nicely, reading the documentation and giving all the information I could think of about my issue, but all the time your answers were, to put it mildly, very disappointing and almost insulting.

Although I am very sure you won’t even budge on this remark of mine, I wish you a good life.

Good bye.

Maybe it’s people asking the same questions over and over again. Yes, I have bumped my head too (last week actually), but I don’t blame Fox. You should be happy to get a response, even if you don’t like it.

Have you even tried reading the forum instead of just asking questions? The answer is there…

https://git.tt-rss.org/fox/ttrss-docker-compose/commit/3ebfd8680667e4a50b622680e1244d4dd4375576

should be fixed now