Serverless-offline: Option to disable `lambdaPort`

[crash7]

Feature Request

In our multiple lambda services we use serverless-offline only for the http/ApiGateway local simulation, and since we use many services with multiple serverless-offline it would be nice if we could directly disable the lambdaPort (to avoid port collisions and resources).

I remember seeing an issue saying something like this but couldn't find it :(

Happy to contribute with a PR, just preferred to open the issue first in case there is something similar in the roadmap.

[ajouve]

Hi,
I exactly had the same issue, all our services are running on 30XX the solution I found is to add set lambdaPort argument to the 40XX ports.

Not a great solution, but you can continue to work :D

[rodrigopasc]

How do you guys are running multiple services simultaneously?

Do you have a script to start them all?

[AshUK]

How do you guys are running multiple services simultaneously?

Do you have a script to start them all?

Yep I have python script with iTerm 2 that launches all the services into new tabs. This won’t scale as the number of services grow but it’s a workable approach for now

[sergioflores-j]

I could get all my services working by setting the lambdaPort as null, e.g.:

serverless-offline:
    lambdaPort: null
    httpPort: 3002