Bash Script that only runs in terminal

bash

I created a Bash script that should be able to be ran on any machine. The problem I'm having it'll only run in terminal. When a user double clicks the script, some users have it open up in iTerm, and some in Xcode in read view. Any idea how to have it execute in these programs or make it only specific to terminal?

Also, I'm having an issue as the script I'm running as its being opened from an "Unidentified developer". I know how to manually resolve from system preferences, but is there anyway to automate in the script?

Best Answer

Add the `.command` extension

To have a bash script open and execute in macOS's Terminal.app, add the suffix .command to the filename.

If you have a bash script called myscript.sh, rename it to myscript.command. Once renamed, when the file is double-clicked or opened from macOS's Finder the Terminal.app will open and execute the file.

Code Signing

The Unidentified Developer warning appears because the script is not code signed. It is a reasonable warning from macOS, as a script could do harm.

If you are distributing the script through a web site, you need to code sign the payload or contents. How to best achieve this depends on your users' environment.

See making an executable bash file run when clicked for reasonable approaches such as an AppleScript wrapper or platypus.

AppleScript Wrapper

You can embed a shell script within an AppleScript. Exported AppleScripts can be made executable and code signed:

 Applications > Utilities > Script Editor.app

Use the do shell script command and File > Export with code signing enabled.

Related Solutions

MacOS – sourcing bash profile for root users

The problem you are encountering is that when you run su by itself, you are not entering a 'login' shell. This means that your environment, working directory, and everything except uid/gid remain the same of the original user.

A simple solution to a simple problem:

su -

From the su(1) man page:

The su command is used to become another user during a login session. Invoked without a username, su defaults to becoming the superuser. The optional argument - may be used to provide an environment similar to what the user would expect had the user logged in directly.

Also:

   -, -l, --login
       Provide an environment similar to what the user would expect had the user logged in directly.

If you su into a login shell, bash will behave as you expect, and automatically source the appropriate files on "login", without the need for overly hacky workarounds.

MacOS – Can’t get commands inside .bash_profile startup script to run

Does your .bash_profile have DOS-style line endings? Strange error messages like that often are "corrupted" by a \r character.