Filament exports under fly.io
Hello everyone,
I don't know if any of you host your filament app on fly.io. I'm now running into the problem that I can't set up the export properly. Filament normally uses queued jobs for this.
When I use the
I tried using the
Where is my error in thinking here? How should it be done correctly? Or in which direction should I think or search?
Thank you very much in advance for your help!
Johannes Nazarov
I don't know if any of you host your filament app on fly.io. I'm now running into the problem that I can't set up the export properly. Filament normally uses queued jobs for this.
When I use the
sync connection, the files are created, but my app reports HTTP 419 “This page has expired”.I tried using the
database connector instead, but this requires a worker to be running to process the jobs. Now fly.io is designed to use a separate process for such tasks. However, the volumes available on fly.io can only ever be connected to one of the processes (or machines in the background). This means that when exporting with the queue, the export files are created correctly on the worker storage and I even receive a notification in my app. But of course I can't download them in the app because they are on the worker storage.Where is my error in thinking here? How should it be done correctly? Or in which direction should I think or search?
Thank you very much in advance for your help!
Johannes Nazarov
