> On Apr 2, 2015, at 12:11 PM, Jason Fleetwood-Boldt <t...@datatravels.com> 
> wrote:
> 
> 
>> On Apr 2, 2015, at 2:58 PM, Gary Tsai <gary.m.t...@gmail.com 
>> <mailto:gary.m.t...@gmail.com>> wrote:
>> 
>> So in the runner I’m actually calling the csv file locally from my desktop.  
>> I’ve seen snytax where they keep it in a tmp folder locally on the desktop? 
>> I’ve also seen people keep their cvs files in the db folder, and running 
>> something like, “heroku rails runner db/your_file.csv”  (<——not sure about 
>> the command or syntax there)
>> 
>> Overall, I just find it strange the rails runner works locally, but not on 
>> heroku (still at the WTF - stage).
> 
> OHH!
> 
> I’m not too familiar with the runner since I don’t use it — but are you sure 
> you can access your local desktop file inside the runner command? I think 
> that’s your problem. The Heroku runner is looking for the file on your dyno, 
> not on your local machine.
> 
> If you CSV is actually deployed along with your app, then you can keep in the 
> db/ folder, yes. 
> 
> I was talking about a strategy that involved people upload CSV files to my 
> app that get processed in background jobs, so in my case I can’t actually 
> include the CSV in my db folder because it isn’t part of my repo. 
> 

Hmm, I’ll do it from the DB folder then, but that seems strange to me, because 
the original implementation of the app was to allow non-techies to use  a rails 
runner (it’s very similar to rake task, but you don’t need to fire-up the app) 
to be able to upload the CSV via the command line with one command.

Let me try upload from the app itself and see.  

If this were a rake task how would you call it from the db folder?  Heroku run 
rake name_of_task db/name_of_csv.csv  (<<—???)




>> 
>>> Perhaps Heroku is detecting your code try to make a disk call and killing 
>>> it for security purposes? It definitely looks like it is killed by the 
>>> platform. 
>>> 
>> 
>> Maybe?
> 
> 
> Sounds like the right explanation to me. 
> 
> -- 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>  
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en 
> <http://groups.google.com/group/heroku?hl=en_US?hl=en>
> 
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Heroku Community" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/heroku/UNhif0CoY8Q/unsubscribe 
> <https://groups.google.com/d/topic/heroku/UNhif0CoY8Q/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> heroku+unsubscr...@googlegroups.com 
> <mailto:heroku+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to