-
Notifications
You must be signed in to change notification settings - Fork 12
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
Re-org doesn't work in heroku according to instructions! #16
Comments
My apologies this project has been on hold for sometime. I'll update it this weekend. I don't use Heroku myself but I'll try to get it running on Heroku anyway.— On Wed, May 28, 2014 at 6:06 AM, Chris Clarke notifications@github.com
|
Thanks! |
Is this issue fixed? |
According to the current instructions in the README, the new re-org which moves the python app to
/gitshots
does not deploy properly.I tried adding a Procfile and deploying a subtree (see https://coderwall.com/p/ssxp5q) but even using this method the heroku logs showed the following errors:
In the end I reverted the last 4 commits to f36e7b3 to get a working setup in heroku.
The text was updated successfully, but these errors were encountered: