Skip to content
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

Provide cleanup #5

Open
DanielSiepmann opened this issue Oct 31, 2015 · 3 comments
Open

Provide cleanup #5

DanielSiepmann opened this issue Oct 31, 2015 · 3 comments

Comments

@DanielSiepmann
Copy link
Contributor

As generated PDFs are not removed, we should provide a scheduler task.

@DanielSiepmann DanielSiepmann changed the title Inform about cleanup PRovide cleanup Oct 31, 2015
@DanielSiepmann DanielSiepmann changed the title PRovide cleanup Provide cleanup Oct 31, 2015
DanielSiepmann pushed a commit that referenced this issue Nov 28, 2015
…r-einheitlich-im-Repository-konfigurie to master

* commit 'de080dcbb3ad16d8dd201a7c40a4dc09caa427ab':
  [TASK] Added sonar configuration
@ghost
Copy link

ghost commented Nov 10, 2016

You also can use a callback function to delete it right after sending it ro client

@DanielSiepmann
Copy link
Contributor Author

Thanks for the hint @rabe69
Which kind of callback do you mean? At the moment we send a Location header to redirect to the file itself, so no more PHP limits are involved in sending and reading the file.
So a callback is only possible inside of the browser. But as there is just a PDF, how can we implement that?

@ghost
Copy link

ghost commented Nov 10, 2016

http://php.net/manual/de/function.register-shutdown-function.php

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant