Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

I signed it!

CLAs look good, thanks!

Hi @armgit5, thank you for sharing your experience with setting up Cloud Storage with Express, that's really helpful to a lot of folks out there since it's such a popular framework.

We don't usually host specific use cases on the README.md file of the library - @fhinkel, what's a better place to host solutions by contributors?

Thank you for your reply, @kinwa91. Please let me know if there is any place I could contribute and share some examples I've been using for my project. I really think it'd be very helpful to others :-) really like your google cloud solutions :-)

Apologies for the delay on this one. And thank you so much! The best way to add a sample is to create a new *.js file in the samples directory, similar to the others already in there. That way, we can add tests to make sure the samples don't break over time. If you'd be willing to do this - we'd really appreciate it!

Hi, thanks for the PR! This would be the right place, would you be willing to wrap it in a tutorial?

Happy New Year 2019 to you all, I wouldn't mind that at all, would really be happy to do it :-)

Thanks again @armgit5! If you need any help submitting the community tutorial - please do let us know!

I'm sorry it takes me a long time, I still want to put those tutorial still. I will definitely come back to you again.