I've got a program that has a small file structure going on and is then ran using
python do_work.py foo bar
I want my Rails users to press a button and have this happen for them, with the result either uploaded somewhere or just thrown to them as a download link or something of the sort - the output of do_work.py
(say, it's result.txt
)
I also want to clarify that the script results in the creation on the filesystem of 3 separate files, which are not text files (which shouldn't matter and isn't really the problem here)
What is the best way to go about it? Can rake run exec Python? More importantly, is this doable on heroku?
I have Python installed on my system but the provided answer by sockmonk doesn't seem to work - it returns nil. Mind you, other commands like ls
seem to work.
Could it be a permissions problem?
def index value = %x( python --version ) render :text => value end
Incidentally, trying this in irb
:
%x(python)
Brings up the Python terminal INSIDE of irb. It will not take params for whatever reason however.
exec("python script.py params",$result); where "script.py" - script name and variable $result save output data.
To do so, you would need to make your script into a proper Python module, start the bridge when the Rails app starts, then use RubyPython. import to get a reference to your module into your Ruby code. The examples on the gem's GitHub page are quite simple, and should be sufficient for your purpose.
Some Python types like booleans, numerics, and strings are converted back to their equivalent Ruby types. Other types like lists and tuples are returned as wrapper classes, which you might want to explicitly convert back to Ruby types.
Your index
method does not work because python --version
outputs its version to STDERR, not STDOUT. If you don't need to separate these streams, you may just redirect STDERR to STDOUT:
value = %x(python --version 2>&1)
This call is synchronous, so after running the script (python do_work.py foo bar 2>&1
), you should be able to read the files produced by it.
If the script is not able to create the files for some reason, you will now see the exception in the value
variable because error messages are usually sent to STDERR.
If you want to separate STDERR from STDOUT, use the Open3 module.
Beware that the script takes some time to run, so the calls may overlap. I would use a queue here to prevent this.
And don't forget to check the data the user enters. Never pass it directly to the script.
It partly depends on the format of the data. If it's not too long and can be rendered directly in the browser, you can just do something like this in a rails controller:
result = `python do_work.py foo bar` render :text => result
And assuming that result is plain ASCII text, the result will go straight to their browser. If the params to do_work.py come from the user you MUST validate them first though, so you don't wind up creating a nasty vulnerability for yourself. Using the system() call would probably be safer in that case.
If you want to send the results back as a file, look at ruby's Tempfile class for creating the file (in a way that won't stick around forever), and rails' send_file and send_data commands for some different options to send back the results that way.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With