-
Notifications
You must be signed in to change notification settings - Fork 244
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
Toto on windows 7, works locally, app crashes on Heroku #64
Comments
Try using toto 0.4.9, which I just pushed. |
Thanks mate, but I don't see 0.4.9 anywhere? Its not under downloads and the source says version 0.4.8 which is the most recent update I can see from 2 days ago? Could you point me to it please? |
Indeed, I forgot to push it to github. I was refering to rubygems.org. You can install it via rubygems with |
I am running toto 0.4.9 locally. I can clone Dorthy and push directly to heroku and all is fine, but if I manually create a txt file in the directory or use the command "rake new" to create a new post heroku barfs the next time I publish. Digging into it a bit, I discovered that the sample post that comes with Dorthy has unix style line endings and the generated windows file has windows line endings. I modified the local git config to have autocrlf set to true using the following statement: git config core.autocrlf true The problem goes away after that. Not sure what you can do about this issue really, but now you at least know the cause. |
NotMyself, I believe that you issue is not related to the original one, so it would be better to report it as a new. But anyway, IMHO, it's not an issue - just use "\n" line endings with your editor (but your way is even better and if my mind is not cheating - autocrlf become true by defualt not far ago). Alternatively you can monkeypatch Toto to use |
I've got Toto up and running on Windows 7. I can go to http://localhost:3000 and see it working.
But no matter what I try it doesn't work once I push to Heroku. I thought maybe adding the URL to
config.ru
was the fix, but no luck.Am I just missing something?
Here's what heroku logs spits out:
The text was updated successfully, but these errors were encountered: