docker support about nitter-rss-proxy HOT 10 CLOSED

I don't really know what I'm doing, but let me know if the Dockerfile that I just committed works for you.

from nitter-rss-proxy.

awesome, i got it working. so am accessing it with
http://localhost:8080/nasa i get the rss
do i have to do anything when rate limit hits? or will it auto change to another instance?

thanks

from nitter-rss-proxy.

Glad that it works!

I'd recommend choosing multiple public instances from the list at https://github.com/zedeus/nitter/wiki/Instances. You can verify that each one is working by running a command like this:

nitter-rss-proxy -user nasa -instances https://nitter.it/

(or whatever equivalent is needed to pass those -user and -instance flags to your Docker image).

Then pass the instances that you chose as a comma-separated list when you run the proxy, e.g.

nitter-rss-proxy -instances https://nitter.it/,https://nitter.ca/,...

The proxy will cycle through the instances as it handles requests, and if an instance times out or reports an error, it'll automatically move on to the next one in the list.

from nitter-rss-proxy.

i dont think i can pass -user or -instance in docker-compose. not as enviroment :(
can it be implemented in main.go getting list from https://github.com/zedeus/nitter/wiki/Instances
just a suggestion.

thanks

from nitter-rss-proxy.

I don't know anything about docker-compose, but do any of the answers at https://stackoverflow.com/questions/37366857/how-to-pass-arguments-to-entrypoint-in-docker-compose-yml help?

I'd rather not make the program automatically get a list of instances for a variety of reasons (it'd add a network dependency on GitHub, the proxy would need to parse that webpage, some instances are flaky or buggy and there would probably still need to be a way to manually exclude them, etc.).

from nitter-rss-proxy.

here is my docker-compose.yml

nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    command: [nitterproxy -instances https://nitter.it/,https://nitter.ca/]

how do i test it now?
if i go to image console and run nitterproxy -instances https://nitter.it/,https://nitter.ca/
i get this error
sh: nitterproxy: not found

from nitter-rss-proxy.

The Dockerfile that I committed installs the executable at /nitter-rss-proxy. Does changing the final line of your docker-compose.yml to something like this work?

  command: [ '/nitter-rss-proxy', '-addr', '0.0.0.0:8080', '-instances', 'https://nitter.it,https://nitter.ca' ]

from nitter-rss-proxy.

ok i changed last line and when i runthe command on console '/nitter-rss-proxy', '-addr', '0.0.0.0:8080', '-instances', 'https://nitter.it,https://nitter.ca' it still says not found.

from nitter-rss-proxy.

It seems weird to me that running /nitter-rss-proxy on the console wouldn't work, but this is beyond my knowledge. The Dockerfile seems pretty trivial and works on Google Cloud Run, so hopefully someone with more knowledge about docker-compose would be able to tell you what needs to be changed in your docker-compose.yml file.

from nitter-rss-proxy.

here is my docker-compose.yml

nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    command: [nitterproxy -instances https://nitter.it/,https://nitter.ca/]

how do i test it now? if i go to image console and run nitterproxy -instances https://nitter.it/,https://nitter.ca/ i get this error sh: nitterproxy: not found

Because the Dockerfile has an ENTRYPOINT entry, the command: ... line in your docker-compose.yml is appended after the ENTRYPOINT line. (more info)

You should change the command keyword in your docker-compose.yml to entrypoint.

nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    entrypoint: ["/nitter-rss-proxy", "-instances", "https://nitter.it/,https://nitter.ca/"]

from nitter-rss-proxy.