Question No --have-registration-token Flag in Linux Server Installer

I tried installing the Accelerator alongside our Cache Server V1 to speed up team workflow for 2019.3.
As we're using Github for collaboration, we just want to use the Cache Server capabilities for Asset Pipeline v2 of the Accelerator.
In the docs, it states that there's a switch for users without teams advances license call --have-registration-token false, but the installer does not know it. Did I do anything wrong?

 

Apologies for that, @pojoih, it's a documentation bug that we are fixing (ticket [COL-1235]). If you want to install an Accelerator to only support the new pipeline, you can use this option: --enable-collab false

Additionally, our tools should always accept a --help option. For example, the installer will show you something like this:

Usage:
--help Display the list of valid options
--version Display product information
--unattendedmodeui <unattendedmodeui> Unattended Mode UI
Default: none
Allowed: none minimal minimalWithDialogs
--optionfile <optionfile> Installation option file
Default:
--debuglevel <debuglevel> Debug information level of verbosity
Default: 2
Allowed: 0 1 2 3 4
--mode <mode> Installation mode
Default: osx
Allowed: osx text unattended
--debugtrace <debugtrace> Debug filename
Default:
--installer-language <installer-language> Language selection
Default: en
Allowed: en
--prefix <prefix> Installation Directory
Default: /Applications/Unity/accelerator
--storagedir <storagedir> Storage Location
Default: /Users/brad/Library/Unity/accelerator
--existing-config <existing-config> Choose how to handle existing configuration
Default:
Allowed: reconfigure replace
--enable-adbv2 <enable-adbv2> Version 2 (New in 2019.3)
Default: true
--enable-legacy <enable-legacy> Version 1 (Legacy)
Default: false
--enable-adb <enable-adb> Accelerate one or both of the asset import pipelines
Default: true
--registration-token <registration-token> Provide a registration token from Unity Collaborate
Default:
--enable-collab <enable-collab> Accelerate Unity Collaborate
Default: true
--enable-cdp <enable-cdp> Send usage statistics to Unity
Default: true

 

Got it, my problem was actually not calling register adbv2 before run. It works flawlessly now.

For future reference: Installing the Accelerator on a Synology NAS Server (Synology DS916+) works, except the Autostart Service. But this can be easily achieved via DSM Scheduled Tasks. Just set up a triggered task for bootup and call this script (paths have to be adjusted of course):

Code (CSharp):

1. /volume1/server/UnityAccelerator/unity-accelerator register adbv2
2. /volume1/server/UnityAccelerator/unity-accelerator run -persist /volume1/server/UnityAccelerator/Cache