Skip to content

NodeCommand is no longer used on AWS #373

Closed
@mtrezza

Description

@mtrezza

(Originally posted here thanks to dblythy)


This is a minor issue, but deploying the sample application trips up on AWS due to:

Unknown or duplicate parameter: NodeCommand

I believe NodeCommand is no longer used on AWS (was previously depreciated in favour of Procfile but I think it’s gone altogether now.

This can be solved by removing these lines:

aws:elasticbeanstalk:container:nodejs:
NodeCommand: "npm start"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions