S3 keys/paths not working (on windows)
See original GitHub issueWhen I deploy to S3 via npm run deploy
it all seemingly works correctly. When I visit my site at the s3 url, I can see everything at index.html except all images are broken and I get 404s when clicking on anything that uses <Link/>
.
When I view my s3 bucket, it seems that all the keys for files which reside inside a folder within the public folder, use back slashes instead of forward slashes (which would mimic a folder in s3).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
S3 keys are not file paths - alexwlchan
The problem. Most filesystems have special path entries that mean “the current directory” and “the parent directory” – on Unix-like systems, ...
Read more >Use and return forward slash in Path sep even on Windows
Number of places in Windows where forward slashes are not allowed is ... S3 keys/paths not working (on windows) jariz/gatsby-plugin-s3#22.
Read more >C# AWS S3 SDK copy object to a different region
How does S3 discover the target region? Are keys (paths) unique across regions also? Also, the target bucket may require different credentials ( ......
Read more >AWS S3 cli isn t working on Windows server - Edureka
There is no problem running it on my Linux box, but when it comes to windows server 12 simple AWS S3 cli commands...
Read more >Top 10 Most Common Errors In GitLab CI Pipelines - Medium
GitLab is not recognizing the configuration deploy review as a job. The problem here is that this job configuration is missing the script...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just ran into this as well, happy to attempt to fix and open a PR.
Edit: I see some updates made to fix this 10 days ago, but last published to NPM 12 days ago. Is this already fixed but just not released yet?
Live on npm @
0.2.5