mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
04e829d457
Using the --dev flag is the only support way to change the internal Kibana environment to something else. Allowing NODE_ENV to be set at all can have unexpected results with our dependencies, so we now always set it to production.
24 lines
639 B
Bash
Executable file
24 lines
639 B
Bash
Executable file
#!/bin/sh
|
|
SCRIPT=$0
|
|
|
|
# SCRIPT may be an arbitrarily deep series of symlinks. Loop until we have the concrete path.
|
|
while [ -h "$SCRIPT" ] ; do
|
|
ls=$(ls -ld "$SCRIPT")
|
|
# Drop everything prior to ->
|
|
link=$(expr "$ls" : '.*-> \(.*\)$')
|
|
if expr "$link" : '/.*' > /dev/null; then
|
|
SCRIPT="$link"
|
|
else
|
|
SCRIPT=$(dirname "$SCRIPT")/"$link"
|
|
fi
|
|
done
|
|
|
|
DIR="$(dirname "${SCRIPT}")/.."
|
|
NODE="${DIR}/node/bin/node"
|
|
test -x "$NODE" || NODE=$(which node)
|
|
if [ ! -x "$NODE" ]; then
|
|
echo "unable to find usable node.js executable."
|
|
exit 1
|
|
fi
|
|
|
|
NODE_ENV=production exec "${NODE}" $NODE_OPTIONS --no-warnings "${DIR}/src/cli_plugin" "$@"
|