This help article is for Enterprise customers and explains how to install the latest version onto their servers using the "command line" approach. There is another approach - fully automated - which requires installing an agent on your server which polls our repository server for updates. This does require, however, firewall changes as non-standard ports are used.
Every time we release a new version, we create a "nuget" package. Think of this like a zip file, which contains all the files and folders in a special format developed by Microsoft.
To download a version of PoolCar you will need to use the nuget.exe command line tool. Yes, the good 'ol command line!
This is a one-time download and needs to be installed on your server, or a staging server:
Note this is NOT software developed by us, i.e. "third party".
The remainder of this document explains how to use the nuget.exe command line program. The URL as specified with the "-source" option is not shown here below for obvious reasons, nor is the username and password to access the repository. Please contact us for these details if you haven't already.
List of all Versions
From the command line:
nuget list PoolCar -source http://secret -allversions
To install the latest version to the c:\inetpub\wwwroot\PoolCar directory:
nuget install PoolCar -outputdirectory c:\inetpub\wwwroot -source http://secret -excludeversion
In the above example, note that:
- -outputdirectory means where you would like the app installed to. Some customers run PoolCar off a driver letter other than "C:" so change the directory as required
- This will create the sub-directory "PoolCar" if it doesn't already exist
- -source is the URL of our repo server, we'll send that to you privately if you request it ;)
- -excludeversion means create the "PoolCar" directory without the version number suffix. If it weren't for this option then the app would be installed to c:\inetpub\wwwroot\PoolCar-22.214.171.124 (or similar)
To install the a specific version to the d:\apps\PoolCar directory:
nuget install PoolCar -outputdirectory d:\apps\PoolCar -source http://secret -excludeversion -version 126.96.36.199
Things to Watch Out For
- As the package name is "PoolCar" it will always create a sub-directory called "PoolCar" underneath the outputdirectory, if it doesn't exist. Your IIS website should point to this PoolCar sub dir. Some customers may have called sub-dir by another name, such as FleetBookings or similar. It is recommended that you rename this folder to "PoolCar" and update IIS accordingly.
- If you do not want to write directly to the app root folder, then we suggest an outputdirectory that is out of the way, such as a temp folder or staging area. You can then copy or xcopy the files from staging to the production folder.
- Avoid version numbers that do not end in a zero as these are test releases destined for QA. Stick to versions that end in a zero as these are considered stable. For example - test 188.8.131.52, stable 184.108.40.206
- If you have a formal UAT process, use pulls only to your UAT server, not production. 'Bubble-up' the UAT candidate once it has passed to your production box via copy or xcopy.
- If your booking receipt emails do not have .ics calendar attachments (and you have enabled this in Application Settings) then you may not have modify permissions on the TempFiles folder. Grant access permission to "Network Service" and "IIS_IUSER" users to this folder.
- The UploadedFiles folder also needs access permission to "Network Service" and "IIS_IUSER" users. This folder is used for exporting Excel files from PoolCar (Booking Search, Vehicle/Driver/Servicing Registers, etc).