Support for serving static files about aws-sam-cli

[PaulMaddox]

Should be quick to add.

https://github.com/gorilla/mux#static-files

[PaulMaddox]

I think it makes more sense to default the public/ for the --public-dir.

Two reasons:

1. The AWS CodeStar Node.JS Serverless project uses public/, so this would work out of the box - great for new customers and demos.

2. I don't think there would be many instances of people wanting to serve up both their Serverless app (java/node.js source) as well as their static assets, so I don't think that matches what people would deploy to AWS in their Lambda deployment package.

To be clear, we'd mount public/ at / on the HTTP listener still.

Thoughts?

[sanathkr]

Agree with 1.
Don't agree with 2. If I am building a serverless website, I need to serve static content.

Can we call it --static-dir instead of public-dir? It makes the intent more clear. Also can we allow multiple --static-dir? Frameworks like expressjs allow this. If a file with same name exists in both places, the directory specified first will take precedence. All of them will mount at / of the HTTP listener.

[PaulMaddox]

Will make the param --static-dir, but I don't think the CLI framework we're using allows multiple, so will have to leave that for now.

PR incoming.

[sanathkr]

Sounds good.

[turjachaudhuri]

Sounds good.

Hi Sanath ,
In serverless there are a few custom plugins which help you in uploading a set of files/folders to a s3 bucket as part of the serverless deploy step.
Is there any alternative like that ?
I want to avoid the step of uploading the files manually .
I want to simply create a bucket as part of my SAM template and then upload files from a specific folder in my local directory to the created bucket.
Is this possible?