```
1. frontend.js: post(file) to graphCool.resolv...
# prisma-whats-newa
albeik
11/10/2017, 5:41 PM Copy code
1. frontend.js: post(file) to graphCool.resolver(file)
2. graphcool.resolver(): post to cloudinary (keys are hidden)
3. do any other updates (if needed)
4. return { cloudinary_url }a
agartha
11/10/2017, 5:42 PMe
emils
11/10/2017, 5:43 PMI don’t like that “outdated” string in url path
a
albeik
11/10/2017, 5:43 PMI did. However, it’s been moved to an
outdatedalbeik
11/10/2017, 5:44 PMSince my app is serverless (hence why using graph.cool as BaaS) I want to make sure that my front-end does not contain any API-keys
albeik
11/10/2017, 5:45 PMUsing a resolver would make sense. Upload a file to the resolver, let it do its thing… and return back to the app. But wanted to check if anyone did a similar approach. 😊
a
agartha
11/10/2017, 5:51 PMYou cannot upload a file to a resolver
agartha
11/10/2017, 5:51 PMBecause you can only call it using a GraphQL query/mutation
agartha
11/10/2017, 5:55 PMIt's in the outdated folder because the file and folder structure are incompatible with the
graphcool add-templatea
albeik
11/10/2017, 5:57 PM@agartha what would be the solution to hide the API keys from the front-end in a serverless app?
albeik
11/10/2017, 5:58 PM@agartha thank you for the clarification on the
outdateda
agartha
11/10/2017, 5:58 PMI would use a lamdba function to post your file to, so there's no key in the client
a
albeik
11/10/2017, 6:06 PM@agartha Gotcha. Would you have a resource in handy as to how one creates/uses lambda functions w/GraphCool? 😅
a
agartha
11/10/2017, 6:07 PMYou can have a look at an older file-proxy example I made. Unfortunately, it's also in the outdated folder 😉 https://github.com/graphcool/templates/tree/master/outdated/file-handling/file-proxy It uses Webtask instead of AWS, but the idea is the same
a
albeik
11/10/2017, 6:07 PMThank you sir!
albeik
11/10/2017, 6:07 PMI’ll take a look
albeik
11/10/2017, 6:14 PM2 Views