Serverless-next.js: How to support multiple environments

[justinwhall]

Hello, is there a way to support multiple environments with the new serverless component? We've upgraded and used to pass env vars to serverless.yml which no longer seems to be an option.

[danielcondemarin]

@justinwhall Would this https://github.com/serverless/components#environment-variables help?

[justinwhall]

I'm not sure. I'm familiar with passing env vars to the serverless.yml but I'm not certain where they would go with the update?

Components are a new concept to me. Perhaps I'm missing something here but as far as the serverless.yml config goes, I'm not certain how both generate or conditionally deploy to different components – or perhaps that wrong terminology. Same component but different Apps.

What I'm after here is a way to build/deploy different environments something like sls deploy --env=stage

Does that make sense?

[justinwhall]

I suppose this is what I'm looking for. Does this package support something like:

myApp:
  component: serverless-next.js
  inputs:
    code: ../

With a directory structure like:

code/prod
code/test

Edit: Ok, no. I see the docs on inputs now.

[skycremaschinin]

Hi,

how could i manage different stages, specifying different cloudfront distributions, buckets and lamba for each stage?

[danielcondemarin]

Hi folks, I've just released @1.3.0 which adds support for custom app directory paths (see here nextConfigDir). Credits to @jayarnielsen for implementing 🙌

I'm closing the issue as you should now be able to do something like:

│   next.config.js    
│
└───pages
│   │   index.js
│   │   users.js
│   │   ...
│   
└───dev
    │   serverless.yml
└───prod
    │   serverless.yml

# dev/serverless.yml
myNextApp:
 inputs:
  domain: [ "dev", "myapp.com" ]
  nextConfigDir: "../"