5.5.0
ForgeBox Enterprise
Installation
Regardless of where you place the box binary, the first time you execute it, a
.CommandBox folder will be created in your user's home directory and CommandBox will be extracted into that location. If you delete this directory, it will be replaced the next time the CommandBox executable is run.You can specify a different install location by adding
-commandbox_home=E:\CommandBox when you run the box binary.To avoid specifying the commandbox_home variable every time you can create a file called
commandbox.properties (case sensitive) in the same directory as the binary, and fill it with this line:1
commandbox_home=E:\\CommandBox
Copied!
The CommandBox home can also be a path relative to the location of the
commandbox.properties file.1
commandbox_home=../boxHome
Copied!
Windows
Extract the executable box.exe from the downloaded zip file, placing it anywhere you prefer where you can then execute it when needed, such as from the Windows command line/terminal. You can also run it directly Windows File Explorer, where you would just double click on the exe,which will open the CommandBox shell in a new terminal window.
Warning On Windows 10 and above, the first time you try to run via Windows File Explorer an exe that you've downloaded, Windows Defender Smartscreen will popup with a warning that "Windows protected your PC". You will need to choose the offered "More info" link and then the offered "Run anway" button, to proceed.
Hint When running from the Windows command line/terminal, you can make it so that you can runbox.exewhile you are in any folder (not just the one where you placed it), by simply adding the exe's location to the WindowsPATHsystem environment variable. See http://www.computerhope.com/issues/ch000549.htm​
When you are finished running commands in the CommandBox shell, type
exit. Or if you ran the box.exe from within Windows File Explorer, you can just close the terminal window which that opened.Mac/ *Unix
Homebrew (Mac)
​Homebrew is a great Mac package manager, it can easily install and keep your CommandBox installation up to date (even binary releases), just run the following for stable releases:
1
brew install commandbox
Copied!
To stay with current bleeding edge releases use the following:
1
brew tap ortus-solutions/homebrew-boxtap
2
brew install --head ortus-solutions/homebrew-boxtap/commandbox
Copied!
Then run the
box binary to begin the one-time unpacking process.Versions will be installed in
/opt/homebrew/Cellar/commandbox. To switch between versions, you will need to install the new version - either using the bleeding edge tap or the main repo. For example to switch to a (very) old version:Copied!
If you are using a tap, and want to revert back to the current stable version
1
brew uninstall ortus-solutions/homebrew-boxtap/commandbox
2
brew install commandbox
Copied!
If you want to use a
commandbox.properties file as mentioned above, even though the symlink is added in /usr/local/bin, your box binary file will be in the /opt/homebrew/Cellar/commandbox/<version>/libexec/bin/ directory where you should place your commandbox.properties file. There will also be a box binary in the /opt/homebrew/Cellar/commandbox/<version>/bin/ directory where you should place the jre if you want CommandBox to use a version of Java that is different from your default version reported by java -version.When using Homebrew to install CommandBox you must use Homebrew for any upgrade, minor or major. To upgrade CommandBox with Homebrew:
1
brew upgrade commandbox
Copied!
NOTE: If you use Homebrew to upgrade your version of CommandBox it will erase your
/opt/homebrew/Cellar/commandbox/<current_version>/ folder. So before upgrading, take a copy of your /opt/homebrew/Cellar/commandbox/<current_version>/libexec/bin/commandbox.properties file to drop back into /opt/homebrew/Cellar/commandbox/<new_version>/libexec/bin/ before running box for the first time after upgrading.Manual Installation
Unzip the binary box and just double click on it to open the shell terminal. When you are finished running commands, you can just close the window, or type
exit.Hint You can place the binary in your/usr/local/bindirectory so it can be available system-wide via theboxcommand in any terminal window.
Linux apt-get
Please note that if you are running Ubuntu 18.04 or greater, or Debian 8 (Jessie) or greater, it's necesarry to have thelibappindicator-devpackage in order to have the tray icon working correctly.
1
sudo apt install libappindicator-dev
Copied!
Run the following series of commands to add the Ortus signing key, register our Debian repo, and install CommandBox.
Stable
( This first install routine also works for the Raspberry Pi. )
1
curl -fsSl https://downloads.ortussolutions.com/debs/gpg | sudo apt-key add -
2
echo "deb https://downloads.ortussolutions.com/debs/noarch /" | sudo tee -a /etc/apt/sources.list.d/commandbox.list
3
sudo apt-get update && sudo apt-get install apt-transport-https commandbox
Copied!
If you do not have Java installed you can install it with the following command.
1
sudo apt install openjdk-11-jdk
Copied!
Then run the
box binary to begin the one-time unpacking process.Linux yum
Stable
Add the following to:
/etc/yum.repos.d/commandbox.repo1
[CommandBox]
2
name=CommandBox $releasever - $basearch
3
baseurl=https://downloads.ortussolutions.com/RPMS/noarch
4
enabled=1
5
metadata_expire=7d
6
gpgcheck=0
Copied!
Then run:
1
sudo yum update
2
sudo yum install commandbox
Copied!
Debian Linux manual install
After you have downloaded the
commandbox.deb file, install it using the dpkg command.1
sudo dpkg -i commandbox-debian-1.2.3.deb
Copied!
Run the
box binary to begin the one-time unpacking process.Redhat Linux manual install
After you have downloaded the
commandbox.rpm file, install it using the rpm command.1
rpm -ivh commandbox-rpm-1.2.3.rpm
Copied!
Last modified 1mo ago