Closed othenos closed 5 years ago
FXLauncher requires nothing special of the http server, so it would be interesting to investigate the actual bucket. Is that possible?
I had some thoughts this morning about whether the cache was the problem. Turns out it was. I think what happened was my experimentation with different servers and different settings left the cache with some bogus files and it prevented fxlauncher to connect and/or update with S3.
So I deleted the local cache, rebuild everything and redeployed to S3. Now it behaves as expected.
I appreciate your offer to help but now it does not seem necessary. Thanks.
Best wishes, Mike
On Thu, Jan 10, 2019 at 12:00 AM Edvin Syse notifications@github.com wrote:
FXLauncher requires nothing special of the http server, so it would be interesting to investigate the actual bucket. Is that possible?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/edvin/fxlauncher/issues/146#issuecomment-452991123, or mute the thread https://github.com/notifications/unsubscribe-auth/AB4jrJVB6rqP8DYNPAidEbztFFFbHmdpks5vBuT7gaJpZM4Z4pYS .
Perfect. Thanks for reporting back :)
This is probably a misunderstanding on my part, but I am trying to use fxlauncher to download the dependencies from an S3 bucket. The bucket has public read permissions. I have a script that uploads the contents of the app/ directory to the bucket. I can access files in the bucket using a standard url from a browser. However, when I try to have fxlauncher do the check & download, it fails with no message as to why.
As a test, I uploaded the app/ contents to a tomcat server and changed the to point to it. Worked just fine.
This is the url I am using for S3 (without the bucket name)