Stringer auto deployed via heroku don't update/fetch news from rss channels

[lajlev]

[mockdeep]

@lajlev can you provide a link to the feed that is not working for you? I'm subscribed to Ars Technica which uses RSS and that works fine for me.

[lajlev]

Now added Ars Technica. On add I get a lot of news, but then I don't get any after that.... [image: image.png]

…

On Thu, Sep 22, 2022 at 8:46 PM Robert Fletcher ***@***.***> wrote: @lajlev <https://github.com/lajlev> can you provide a link to the feed that is not working for you? I'm subscribed to Ars Technica which uses RSS <http://feeds.arstechnica.com/arstechnica/index/> and that works fine for me. — Reply to this email directly, view it on GitHub <#647 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABAVTCDNWUPFJOEGIGKFRTV7SSRVANCNFSM6AAAAAAQS6DEJQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Med venlig hilsen Michael Lajlev

[mockdeep]

I've spent some time looking into this. I have an existing instance that doesn't have this problem, but if I deploy a new copy using the Heroku button in the README it doesn't get updated feeds for some reason. When I ran heroku run rake work_jobs it fetched the feeds. I suspect the difference is that I have an APP_URL set in my instance. Can you try configuring it on your app like this?

$ heroku config:set APP_URL=`heroku apps:info --shell | grep web_url | cut -d= -f2`

I've set it on my test instance and I'm waiting to see if that works.

[mockdeep]

Okay, following up on this. Setting APP_URL did the trick for me on a new deployment. I gather what happens is that when the scheduled job runs it first pings the app to boot it so that it will handle jobs. I'll leave this issue open for now as I think we can probably come up with something a little better. Now that Heroku is retiring their free plans, we'll be required to upgrade to paid plans anyway, so probably the easiest thing is to upgrade your Heroku account, or try deploying to another service.