-
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
Running a ruby app via cocaine-tool #5
Comments
Okay, I have managed to run my ruby app through the python app and discovered
|
Hey @3Hren can you help here? |
Well, seems like this 9d680e3 commit ruins everything since it just returns ancient behavior for reasons I can't understand myself. Maybe I was drunk or something else. I'll retest and probably revoke this commit. For now, try 0.12.0-rc22 version, should help. |
I guess I have found the main problem: the highest cocaine-core version contained in the package repo from the example is 0.11.0. It seems that it is not compatible with this gem of version 0.12.*. |
Hello, I am trying to run a simple ruby app like the qr-code generator from the tutorial (https://github.com/cocaine/cocaine-vagrant) and I can't understand some things.
manifest.json
so the app could be started? I have used this configuration andcocaine-tool app start
tells me everything is fine:It seems like it does not work at all, because in case of python app I see this when do an http request and call ps:
And this is the case of ruby app and the request hangs until I
cocaine-tool app stop
the ruby app:--debug all
option forcocaine-tool
commands but it does not seem useful at all. Also, I was trying to read the /var/log/cocaine-python-proxy.log file and its content was not any more helpful:cocaine-framework-ruby
gem:Still I have no idea what can I do inside a block to respond with something: in
cocaine-framework-ruby
gem it is said thatCocaine::TxChannel
is a Writer channel and should be used for patching the response, but the problem is that it does not have any public methods on it.The text was updated successfully, but these errors were encountered: