Overview

  1. Apple sandbox
  2. Security permissions
  3. Applescript® resources
  4. Bash resources
  5. Tips

1. Apple sandbox

MaScriptRunner is entirely Apple® sandbox compliant.
If you like to know more about Apple® sandbox technology, go to "apple.com"

2. Security permissions

Security pop-up

Those kind of pop-up windows are completely normal. You need to give access to maScriptRunner to talk against other applications. In this particular case you need to give access to maScriptRunner to run Applescripts, what is the main reason to run maScriptRunner. Only Applescripts that are stored inside a folder that you defined within maScriptRunner. IMPORTANT: If you applied "auto restart" in the preferences panel of maScriptRunner, you need to give access to maScriptRunner to restart himself. MaScriptRunner will not execute or interact with other applications as long as you do not give permission to do so.


(!) REMARK: Those kind of permissions must be given only once, on the first run of maScriptRunner or a particular script.


Applescript

Afterward, the system knows that you trust maScriptRunner. We suggest to code sign your own Applescripts to be compliant to Apple's security standards, therefor you need an Apple Developer ID.
How to do this? It is clearly explained at "macosxautomation.com" or at "developer.apple.com"

3. Applescript® resources:

4. Bash resources:

5. Tips:

maScriptRunner will run all your selected scripts in an endless loop, but sometimes you might like to run a script at a certain time of the day.

We will show you one way how to do this.
Using this piece of Applescript® at the highest level of your own script: