Fixed bad exit code
In Bash, code 0 is success, non-zero is failure. In the meantime I've added || true to the end of the call to blueprint.sh so the Docker image can build, but changing this to 0 is cleaner.
This commit is contained in:
parent
af114490dc
commit
dc90671ec0
1 changed files with 2 additions and 2 deletions
|
@ -284,7 +284,7 @@ if [[ $1 != "-bash" ]]; then
|
||||||
dbAdd "blueprint.setupFinished"
|
dbAdd "blueprint.setupFinished"
|
||||||
# Let the panel know the user has finished installation.
|
# Let the panel know the user has finished installation.
|
||||||
sed -i "s/NOTINSTALLED/INSTALLED/g" $FOLDER/app/BlueprintFramework/Services/PlaceholderService/BlueprintPlaceholderService.php
|
sed -i "s/NOTINSTALLED/INSTALLED/g" $FOLDER/app/BlueprintFramework/Services/PlaceholderService/BlueprintPlaceholderService.php
|
||||||
exit 1
|
exit 0
|
||||||
fi
|
fi
|
||||||
fi
|
fi
|
||||||
|
|
||||||
|
@ -2215,4 +2215,4 @@ if [[ ${VCMD} != "y" && $1 == "-bash" ]]; then
|
||||||
# This is logged as a "fatal" error since it's something that is making Blueprint run unsuccessfully.
|
# This is logged as a "fatal" error since it's something that is making Blueprint run unsuccessfully.
|
||||||
PRINT FATAL "'$2' is not a valid command or argument. Use argument '-help' for a list of commands."
|
PRINT FATAL "'$2' is not a valid command or argument. Use argument '-help' for a list of commands."
|
||||||
exit 1
|
exit 1
|
||||||
fi
|
fi
|
||||||
|
|
Loading…
Reference in a new issue