Deployment profiles are used for transferring files from a server to the clients.
When added to an executable, files are transferred to the client before game launch. They can also be used for manual deployment through Manager → Deployment Tab
For any game or application you want to create a deployment profile for you have to:
1. Install the game or application somewhere (a client,server it does not really matter)
2. Move the files to a location where either a. Gizmo server OR b*. the clients have access to these files
Some possible locations are: A shared folder on a Server, a local folder on the Gizmo server (not shared), a NAS etc as long as either the server or the clients have read access to that folder.
3. Create a deployment profile for that game. the Deployment Profile holds all the information necessary for Gizmo to know what to copy and where.
(At the moment you can only create a deployment profile using the application management, so just go to manage-applications and add a new application. fill in the required fields and add an executable. Just enter any path -you are not going to use that anyway - and add a deployment profile to the executable.)
3a. Name = something to remember it by
3b. Source. this is important. add the path to the game or application. it can be a local drive or a unc path (like \\server\steam), as long as either a. Gizmo server OR b. the clients have access to these files
3c. Destination = where the game/application will be copied to (on the clients). Usually c:\program files\"application name"\
NOW, IF THE CLIENT CAN ACCESS THE FILES, CHECK "DIRECT ACCESS"
IF THE SERVER CAN ONLY ACCESS THE FILES, DO NOT CHECK "DIRECT ACCESS"
Check mirror only if you want any extra files inside the destination folder to be deleted. Save the profile.
More info on "direct access" here: http://support.gizmopowered.net/index.php?/Knowledgebase/Article/View/115/15/deployment---direct-access-explained
*If you want to use the deployment profile for manual deployment (Deployment Tab) the files must be accessible BY THE MANAGER(uncheck DIRECT ACCESS). This means that the source path must be relative to the MANAGER you are deploying from.