Heroku Deployment Issue

[noellarkin]

Error when attempting to deploy RSS Bridge in a Heroku app.

To Reproduce
Using https://heroku.com/deploy?template=https://github.com/RSS-Bridge/rss-bridge as mentioned in documentation

Expected behavior
It should deploy RSS Bridge as a Heroku app

Screenshots

Desktop (please complete the following information):

• OS: Win10
• Browser: Chrome

[Bocki]

Is there more log?

[Dag]

The repo is blacklisted for some reason.

This worked successfully:

diff --git a/app.json b/app.json                                                                          
index f184799..216a4b7 100644                                                                             
--- a/app.json                                                                                            
+++ b/app.json                                                                                            
@@ -2,7 +2,7 @@                                                                                           
   "service": "Heroku",                                                                                   
   "name": "RSS-Bridge",                                                                                  
   "description": "RSS-Bridge is a PHP project capable of generating RSS and Atom feeds for websites which don't have one.",
-  "repository": "https://github.com/RSS-Bridge/rss-bridge",                                              
+  "repository": "https://github.com/dvikan/rss-bridge",                                                  
   "keywords": ["php", "rss-bridge", "rss"]                                                               
 } 

[Bocki]

XXII. Access a third-party web property for the purposes of web scraping, web crawling, web monitoring, or other similar activity through a web client that does not take commercially reasonable efforts to identify itself via a unique User Agent string describing the purpose of the web client and obey the robots exclusion standard (also known as the robots.txt standard), including the crawl-delay directive;

Well, they are sort-of-right ;)

So yeah.. the easiest would be to fork the repo and then deploy the heroku service from there. Button should stay the same.

[Dag]

It's not enough to fork the repo bockiii. I tested with a fork. It was also necessary to apply the diff I pasted above.

[Bocki]

you're right, I implied that.

So in order for the heroku deployment to work, the app.json needs to aim at a repo that is not blacklisted, which should be any fork that is not the main repo.

So, I would close this. It wont help to appeal to heroku since we are doing exactly what they do not want (scraping, ignoring robots.txt etc).