-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting to work on Heroku? #1
Comments
Possibly because there is nothing hosted at the root of the site? Try As you can tell it's slapped together, sometimes confused and not stable. Gio
|
Hi! |
We've bypass heroku deploy and use EC2 ourselves now. Feel free to reopen if you want to do this yourself |
If you've gotten it working on EC2, I'm happy to look at Heroku deployment. Heroku's way more accessible to a lot of newsrooms, would probably help adoption to have it available. As the person opening this issue — if you like, I can take a look at it sometime in the next week or so? |
That'd be great if you could. We've been suring up different features but @giovannic and I have struggled to find the time. What better time to implement a refactor than 16:30 on a Friday afternoon! PS: apologies for closing this prematurely, I assumed it'd been opened by myself |
Hi!
We're wanting to try it out here at The Times but I'm having issues getting it working on Heroku. I've added Twitter API keys and changed the Procfile to
web: gunicorn --bind=0.0.0.0:$PORT twitter:app
(I've also added Gunicorn to requirements.txt), but when I connect I get a 404. Any help?The text was updated successfully, but these errors were encountered: