Questions about publicFolder?

[scripting]

I posted more info about publicFolder today on my blog as the Electron app is taking shape.

If you have questions -- here's a place to ask them.

[davisshaver]

Fun to start playing with @scripting, I got the hello world running today.

First gotcha was that relative path ~/Desktop/publicFolder didn't work but switched it to absolute path & all good now.

AWS config I had from an earlier project so this part "just worked". S3 was no problem though I agree with you about Amazon being smart to simplify the signup flows.

Biggest question I'm wondering at the minute, if I were to setup something like public.davisshaver.com & I wanted to manage from more than one computer... is there any safe way to do that? First idea jumps to mind is "disableRemoteDeletes" or something in the config but wondering what you thought.

[scripting]

Use Dropbox! :-)

Pretty sure you can put the watchfolder in Dropbox.

Then you can do it from multiple machines.

On Sunday, September 17, 2017, davisshaver [email protected] wrote:

Fun to start playing with @scripting https://github.com/scripting, I got the hello world running today.

First gotcha was that relative path ~/Desktop/publicFolder didn't work but switched it to absolute path & all good now.

AWS config I had from an earlier project so this part "just worked". S3 was no problem though I agree with you about Amazon being smart to simplify the signup flows.

Biggest question I'm wondering at the minute, if I were to setup something like public.davisshaver.com & I wanted to manage from more than one computer... is there any safe way to do that? First idea jumps to mind is "disableRemoteDeletes" or something in the config but wondering what you thought.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/scripting/publicfolder/issues/3#issuecomment-330068992, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O1i6F1RoREZWSugUfyJTRIzS9g9Aks5sjWaYgaJpZM4PaLjS .

-- Typed on an iPad with fat fingers.

[davisshaver]

Heh of course 💡 . Although I wouldn't mind phasing out Dropbox eventually. Only snag I see is if Dropbox fails to update before starting publicFolder but hopefully that's an unlikely occurrence.

[johkla]

i apologise but i have looked everywhere and tried everything but i am unable to find a solution to PublicFolder not uploading my files. mind you i am not very smart. i am just trying to find something that works bit like a one way Dropbox for serving a static website.

i know the WatchFolder works and that my aws credentials are correct. (the same credentials work when i log into the aws console on the web.) so the problem must be with either :

1. the location or format of the credentials.txt file. this file is stored in the .aws directory in my users directory i.e. ~/.aws and looks like this:

2. or with the settings nominated in the config.json file

i have tried several versions of formatting the information in the credentials.txt file none of them solve the problem.

what am i doing wrong? i'm pretty sure the problem must be that publicfolder is not able to communicate with s3 or am i looking in the wrong place? any ideas much appreciated. johannes

i also tried creating a new AIM user...

[johkla]

thanks! this is the JSON file attached to the user/permissions...

{ "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "s3:GetAccessPoint", "s3:PutAccountPublicAccessBlock", "s3:GetAccountPublicAccessBlock", "s3:ListAllMyBuckets", "s3:ListAccessPoints", "s3:ListJobs", "s3:CreateJob", "s3:HeadBucket" ], "Resource": "" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:", "Resource": "arn:aws:s3:::*" } ] }

[johkla]

thanks! but weird : i can't find the comment on github to reply to it. anyway here is the JSON file

{ "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "s3:GetAccessPoint", "s3:PutAccountPublicAccessBlock", "s3:GetAccountPublicAccessBlock", "s3:ListAllMyBuckets", "s3:ListAccessPoints", "s3:ListJobs", "s3:CreateJob", "s3:HeadBucket" ], "Resource": "" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:", "Resource": "arn:aws:s3:::*" } ] }

On 9 Feb 2020, at 6:27 pm, superchink [email protected] wrote:

Can you log into the AWS console, navigate to IAM, select the user that corresponds to the access key you are using, select Permissions, and paste the JSON from the active policy there here? It’s possible that the user doesn’t have access to the S3 bucket.

Some examples and more detail here: https://aws.amazon.com/premiumsupport/knowledge-center/s3-console-access-certain-bucket/

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.