Prisma

Tangent, I have been using <https://ngrok.com/> to setup a tunnel to my local machine when I’m developing functions. The ‘replay’ functionality is really useful, you can trigger the request (whatever that looks like for your app) and then just replay it over and over for development.

small tips about ngrok to, you can use a `.ngrok.yml` file and have more than one endpoint if you need to try different function at the same time

<@U5Z2AG74M> and at that point, a single Express instance might make more sense.

And then you could actually share quite a bit of code.

we talked about ngrok on the podcast the other day

It’s so nice for any kind of user triggered action (especially filling out a form) to only have to do it once, and then be able to hit replay

This is probably a question for <@U0RQY0KK5> - are there plans to improve the dev/staging/production functionality for Graphcool. I know you can clone a project, but that doesn’t quite do it.

I know about that they are apparently working on the cli to be able to extract save all the data from the console (function, permissions etc…) so when this is done I’m pretty sure re-deploy on another project will be easy and so can switch different environments like that.. i guess

just for the code sharing it looks possible with a config like that in the serverless.yml config file so you probably don’t need any hack for that
```
package: 
  include: 
    - ../common
```

I realized that Now also supports other cloud providers - so looks like we could still use Now, but with AWS under the hood. <https://zeit.co/blog/universal-now>

They just don’t have a wawy to deploy 15 functions at once, do they?

you have to write some funky domain aliases to have them on a single domain

the Now docs are really obscure about this

I got some info here <https://twitter.com/wesbos/status/893551720416071680>

I specified a `name` and `alias` in my `now.json` so that I get the funky URL when I deploy (`now`). I treat that like a staging URL, then to set it to production, `now alias` switch it over to ‘live’

But not ideal to do for a whole bunch of functions

oh yah - I do that for thje <http://syntax.fm|syntax.fm> site, but I just don’t get how to deploy 15 different functions at once

do I need to have 15 different package.json files?

Good lord - that’s quite a variety of responses to your tweet.

I think you do need a different package.json for each one. They’re all going to have different deps

for your question yes you need to have different package.json file if you have any dependencies you want to load on every function