Skip to content

startup.sh doesn't stop on failure #1

Description

@sorccu

Looks like startup.sh doesn't stop even if a step fails. For example, if db:migrate or assets:precompile fail, the app will still start and think it's running OK, when in reality nothing's working. I would recommend a simple set -e or the slightly better set -eo pipefail as the first thing in startup.sh. In fact it should be in every script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions