- I wanted to play with publicfolder, but I couldn't find the files I was saving either in the AWS console or Transmit (which can read and write to S3). publicfolder was showing no errors, either on the command line or in the Electron app.#
- I then went to the aws cli, which can list files in a bucket with 'aws s3 ls s3://bucketname/ ', and it gave me the mysterious output 'PRE /'.#
- I eventually found the files with 'aws s3 ls s3://bucketname/ --recursive', which showed me my files had been saved with a slash as the first character of the filename. ❓#
- To make a long story short, in the config for publicfolder I had forgotten the trailing slash for "watchfolder" (of course the sample config includes the trailing slash). By changing it from "/Users/shanson/myFolder" to "/Users/shanson/myFolder/", the bad files were deleted from S3 and files with proper filenames were uploaded.#
- Watch your slashes!#
- I wanted to play with publicfolder, but I couldn't find the files I was saving either in the AWS console or Transmit (which can read and write to S3). publicfolder was showing no errors, either on the command line or in the Electron app.#
- I then went to the aws cli, which can list files in a bucket with 'aws s3 ls s3://bucketname/ ', and it gave me the mysterious output 'PRE /'.#
- I eventually found the files with 'aws s3 ls s3://bucketname/ --recursive', which showed me my files had been saved with a slash as the first character of the filename. ❓#
- To make a long story short, in the config for publicfolder I had forgotten the trailing slash for "watchfolder" (of course the sample config includes the trailing slash). By changing it from "/Users/shanson/myFolder" to "/Users/shanson/myFolder/", the bad files were deleted from S3 and files with proper filenames were uploaded.#
- Watch your slashes!#