The essential line is the source command, which I discovered by looking at this Knowledge Base article. The PATH lines similarly aren’t necessary in the most basic versions, but might be for any other Linux commands you expect to run. This might not be necessary just to run the tsm commands, but it will pay dividends if you are doing anything more complex along with it. The first line tells it to use the BASH interpreter, rather than the most basic shell. The early lines tell the the operating system how to set up the environment, which is essential because it’s possible the script is run in contexts where the environment is different than the interactive shell you are logged into.

Without them, you’ll get a message like: line 3: tsm: command not found You’ll notice that the script has several lines before it gets to any tsm commands. # any other tsm commands or other bash commands PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:usr/bin:/sbin:/bin' To run tsm commands from a script, we have to make sure our environment is always specified correctly. And even then it may still fall over when run via cron. It’s very common for the same set of commands you just typed in to not work at all when you put them in a shell script. Shell scripting on Linux, particularly when you want to schedule using cron, have a lot more quirks than you’d think at first glance. This post discusses how to get things working on Linux – if you need to automate on Windows, take a look here. But both Windows and Linux have their own quirks, especially when you want to fully automate a process. Finding the commands to do what you want to do in Tableau – that’s the easy part these days. One of the great advantages of tsm is that it is a fully functioning shell / command-line system that works the same on Linux or Windows.

Tradeskillmaster api down