Skip to content

Commit df76d83

Browse files
❗️ Fix shebang so shell scripts work on more systems (#955)
In general, `#!/usr/bin/env bash` is considered better practice because it's more portable. Bash is not always located at /bin/bash. This will make the scripts work on systems, like NixOS
1 parent f8b22c6 commit df76d83

File tree

6 files changed

+8
-6
lines changed

6 files changed

+8
-6
lines changed

next/.husky/pre-commit

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
#!/bin/sh
1+
#!/usr/bin/env sh
22

33
#npx lint-staged --allow-empty

next/entrypoint.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#!/bin/env sh
1+
#!/usr/bin/env sh
22

33
cd /next
44
dos2unix wait-for-db.sh

next/prisma/useSqlite.sh

+2-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
1-
#!/bin/bash
1+
#!/usr/bin/env bash
2+
23
cd "$(dirname "$0")"
34

45
sed -ie 's/mysql/sqlite/g' schema.prisma

next/wait-for-db.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#!/bin/sh
1+
#!/usr/bin/env sh
22

33
host="$1"
44
port="$2"

platform/entrypoint.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#!/bin/sh
1+
#!/usr/bin/env sh
22

33
host=db
44
port=3306

setup.sh

+2-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
1-
#!/bin/bash
1+
#!/usr/bin/env bash
2+
23
cd "$(dirname "$0")" || exit 1
34

45
# The CLI will take care of setting up the ENV variables

0 commit comments

Comments
 (0)