setup.sh fails when run from the scripts directory

[geevarghesekthomas84-sys]

Description

Running ./setup.sh from the scripts directory fails because the script resolves paths relative to the current working directory.

Steps to reproduce

cd hyperswitch/scripts
./setup.sh

Actual behavior

chmod: cannot access 'scripts/notify_scarf.sh': No such file or directory
chmod: cannot access 'scripts/notify_scarf.sh': No such file or directory

Expected behavior

The setup script should work when launched from either the repository root or the scripts directory.

Cause

The script references scripts/notify_scarf.sh relative to the current directory. When launched inside scripts, it looks for scripts/scripts/notify_scarf.sh.

Other repository-relative paths, such as config/docker_compose.toml, are also affected.

Suggested fix

Add this immediately after set -Eeuo pipefail in scripts/setup.sh:

# Resolve the repository root from this script's location.
SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
cd -- "${SCRIPT_DIR}/.."

This sets the working directory to the repository root before the script accesses repository-relative paths.

Workaround

Run setup from the repository root:

cd hyperswitch
./scripts/setup.sh