-
Notifications
You must be signed in to change notification settings - Fork 1
Updating an existing installation
This information applies to the Windows version of Fleet Manager only. Updating a Docker-based installation can be done simply by referencing the right tag in your Docker Compose file (or whatever you use to orchestrate your containers).
To update an existing installation, open up your preferred console in the location where you've extracted the installer CLI (e.g. C:\apps\fminstaller
, if you've followed the instructions on the Installation page).
You should be able to type
C:\apps\fminstaller> fm-installer
and have something like
__ _ _
/ _| |___ ___| |_ _ __ __ _ _ _ __ _ __ _ ___ _ _
| _| / -_) -_) _| ' \/ _` | ' \/ _` / _` / -_) '_|
|_| |_\___\___|\__|_|_|_\__,_|_||_\__,_\__, \___|_|
INSTALLER |___/
Please invoke with a command - the following commands are available:
Service:
install - Registers Fleet Manager with Windows Service Control
uninstall - Unregisters Fleet Manager from Windows Service Control
Installation:
extract - Extracts Fleet Manager binaries into the specified path
list - Lists available Fleet Manager binaries
update - Updates an already-existing Fleet Manager installation
Configuration:
wizard - Starts the configuration wizard
Invoke with -help <command> to get help for each command.
Exit code: -1
printed as output.
Now, figure out the path to the Fleet Manager installation you wish to upgrade, and then save it to the fmpath
environment variable – e.g. like
> set fmpath=C:\apps\fleetmanager
if you installed Fleet Manager in C:\apps\fleetmanager
. Setting the fmpath
environment variable works as a "context" for further commands to the installer CLI that require that particular setting.
To update Fleet Manager, simply issue the update
command, which should produce output similar to this:
> fm-installer update
__ _ _
/ _| |___ ___| |_ _ __ __ _ _ _ __ _ __ _ ___ _ _
| _| / -_) -_) _| ' \/ _` | ' \/ _` / _` / -_) '_|
|_| |_\___\___|\__|_|_|_\__,_|_||_\__,_\__, \___|_|
INSTALLER |___/
Loading list of remote binaries...
Working on Fleet Manager installation here:
C:\apps\fleetmanager
This will UPDATE your current Fleet Manager installation from 4.2.0 to version 4.2.4 - would you like to continue? (y/n)
Creating backup of current installation 100 %
Current installation successfully backed up as C:\ProgramData\RebusFM\FMInstaller\backups\fm-backup-20201117-111132-1.zip
Stopping Windows Service FleetManager... OK
Unzipping fm-4.2.4.zip into C:\apps\fleetmanager... 100 %
Starting Windows Service FleetManager... OK
Fleet Manager was successfully updated.
In case you think something is missing on the documentation wiki, please feel free to raise an issue and let us know: Click here to raise an issue
Overview
Areas
- Connecting Rebus Instances
- Configuring the Fleet Manager Plugin
- Failed Messages
- Delayed Messages
- Message Auditing
- Alerts
- Notification Groups
- Integrations
- Data
- Authentication
- External API
Self-hosted (on-premise/Docker)