[macOS] brew cask install filebot

[rednoah]

The easiest way to install FileBot on Mac OS X and setting up the filebot console tools is to just have brew package manager do it all, fully automatically.


Since Apple does not allow command-line tools in the Mac App Store you will need to install the filebot console tools via brew even if you have already bought FileBot from the App Store.


In Terminal do:


If you're feeling lazy you can install or upgrade the FileBot Command-Line Tools by running the following command:

Code: Select all

sh -xu <<< "$(curl -fsSL https://raw.githubusercontent.com/filebot/plugins/master/installer/app.sh)"

If you feel like running each command yourself step by step, please follow the instructions:


1. Install brew:

Code: Select all

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

brew may require the Command Line Tools for Xcode and the easiest way to get them is running xcode-select --install or installing Xcode via App Store.

2. Update brew package index:

Code: Select all

brew update && brew upgrade

3. Install FileBot:

Code: Select all

brew cask install filebot

Check if filebot is working:

Code: Select all

filebot -script fn:sysinfo

If you want to upgrade filebot you can run:

Code: Select all

brew update && brew upgrade && brew cask install filebot

If you want to uninstall filebot you can run:

Code: Select all

brew cask uninstall filebot

If you have $PATH issues when running filebot (e.g. if /usr/local/bin is not in the $PATH) then you may use the absolute path to the executable:

Code: Select all

/usr/local/bin/filebot

If you want understand what is executed exactly when you call filebot you can run:

Code: Select all

ls -l `which filebot`

[nomaed]

This has been very helpful!

However, one should be careful with brew upgrade, especially in the script for lazies.

It will upgrade all installed brew packages on the system to their latest versions. If you installed specific versions of software and rely on them in your workspace, stuff may break if any new packages have breaking changes in their APIs, for example.