this is unfortunately my second time typing this out since googlegroups never posted my first message.
here’s my deal:
working on a rails app where the user fills in some form data and then with the given info i build a pdf with pdf-writer. after the pdf generates i want to have a link created on the next page for the user to download the pdf to their local machine. few questions: where’s the best place to store the pdf in the rails tree (i imagine somewhere in public) for the user to be able to download it. also, since many users will be using this interface i need a mechanism to junk stale reports. i suppose it could be done with a cron or backgroundrb type deal where it compares the timestamp of the file and the current time and deletes the file after a certain amount of time has passed (probably have a mechanism to regen the reports anyway)…
this is unfortunately my second time typing this out since googlegroups never posted my first message.
here’s my deal:
working
on a rails app where the user fills in some form data and then with the
given info i build a pdf with pdf-writer. after the pdf generates i
want to have a link created on the next page for the user to download
the pdf to their local machine. few questions: where’s the best place
to store the pdf in the rails tree (i imagine somewhere in public) for
the user to be able to download it.
It may not be a problem, but if you put the generated file into the
public tree somewhere, then that file is available for anyone to
download. If you store it outside your public tree you will need
to serve it up with a controller action that utilises send_data
also, since many users will be
using this interface i need a mechanism to junk stale reports. i
suppose it could be done with a cron or backgroundrb type deal where it
compares the timestamp of the file and the current time and deletes the
file after a certain amount of time has passed (probably have a
mechanism to regen the reports anyway)…
It may be possible for BackgroundDRB to look after this. If your
controller passes the request to a background worker, the controller
action may be able to clean up the file after download is
complete. I’m not sure about this one though.
Maybe someone who has a better knowledge of BackgroundDRB would be able to answer this part better.