Use Boxes Editor for initial project setup. After that try running project using other utilities.
All utilities read same license key stored via Boxes Editor "License" screen. If it is server-only installation without GUI you may have no access to the Editor to set license key. In that case you can pass license key via "-license" parameter to all command line utilities.
Example of the License screen.
Servers run unattended. Reco utility helps with basic unattended processing:
For Windows deployment simply install full Windows package on the server and use Reco utility in Windows Scheduled Tasks to run it in automated mode. You can also use any other scheduler that triggers and executes external processes.
For Linux deployment use Linux package and copy files to server. Schedule Reco utility via crontab. Make sure current directory is the directory Reco runs from.
Basic server setup with Reco utility gives you most flexibility since you can choose when to run processing. It is good for over-night or specific schedule processing. But it takes time to setup and test.
Package comes with Server utility. Server will scan specific folders for incoming files and process them automatically.
Moving is not much different from "Server Deployment" listed above. Simply perform server deployment and then move ".box" project files to new machine.
If you have any custom batch or bash files make sure directories they use are changed to reflect new environment.
If you no longer have original setup program or zip file you might need to download new version of the product from this website. In this case you will most likely perform upgrade since version you have might be much older than newly downloaded version.
Upgrades are much more time consuming. Software should be retested to make sure recognition is not worse on your specific images and projects. Please send feedback if recognition accuracy has decreased due to upgrade to new version.
We recommend storing original setup installer or zip files on a backup drive in case if you want to rollback to prior version of the software.
This is important concept for command line utilities.
When you open command prompt on Windows or Bash shell on Linux and navigate to directory using
directory is your current working directory. Now any program you start will use that working directory to find
configuration and resource files it needs to run.
Server program uses resources such as HTML pages to display web interface. If server program is not started from the directory where it is installed then it will not find HTML page files and fail to start. Same applies to other command line tools.
This is less obvious when command line utilities get started by scheduling tools like cron or Scheduled Tasks.
If current working directory is not setup then command line utility will start and fail.
One of the simple ways to make sure that current working directory is correct - use batch or bash script.
Create small batch or bash script that performs
cd just before it runs command line utility. Then use
that script inside scheduling tool.