-
Notifications
You must be signed in to change notification settings - Fork 381
stdin/stdout don't behave like UNIX with heroku run
#256
Comments
/cc @ryandotsmith |
+100 |
We could detect if stdin is a tty and suppress the "attaching process to app" message when piping things around as well |
+1 |
For what it's wroth, pipes work with pg:psql |
@ddollar
This just outputs my list but the data never reaches my rake task (which is checking STDIN). In my rake task, I specifically check that STDIN is not tty (I only want to check for piped input). Not sure how that relates to what @kennethreitz is saying above. Any and all suggestions would be appreciated. |
(But I also don't know much about TTYs.) |
+1 wish stdin could pipe to heroku run |
For some types of operations, e.g., loading data or fixtures into a site, the alternatives to stdin are pretty lame: I either have to upload the data to a public file server and write my import utility to access that (thank goodness for python requests library ;) ) , or I have to commit the file to my repository temporarily, push, remove, commit. For some types of regular operations I'd like to do, neither of these is a very viable option. |
👍 |
bump 👍 |
👍 👍 |
Merged #811. |
Trying to run this command
The pipes should all get hooked up correctly in a non-interactive mode to let stdin/stdout work properly with the shell container of heroku run.
Let me know if this doesn't make sense and I can try to elaborate.
The text was updated successfully, but these errors were encountered: