In order to manually publish all the Newired content to the delivery server, follow the following steps.
I - DOWNLOAD THE DEPLOYMENT PACKAGE
Press Download Selected Journeys button.
Your browser will download a ZIP file (the default name is "launcher.zip") to your computer.
Upload the extracted launcher.zip file to the deployment location configured during Newired platform installation.
II - DEPLOYMENT OF THE CONTENT
Move the previously exported launcher.zip file into a folder managed by the web server. By default it could be something like:
Unzip the launcher.zip into the folder.
TIP: On *NIX operating systems, verify the correct file permissions.
Finally, test the access to the files served by the web server using a web browser, as in the following example:
If the folder and the files are accessible, you should see the Newired launcher in the target application in case you are installing Journeys:
Note that the Launcher is a feature available only for Journeys, as Tips work like tags connected to given elements and do not require a definite starting point. In case your license allows you to author Tips only, this information does not apply.
Customizing the Package for a Specific Folder
If you cannot deploy the launcher.zip archive in the "standard" folder such as <web root>/launcher, then it is possible to upload it to a different folder, according to the actual web server configuration. However, in this case an additional step is required in order to configure the launcher to work correctly.
For example, suppose you need to have the launcher archive in a folder such as:
var NW_launcher_path = '/another_path/additional_folder/launcher_folder/';
This configuration ensures that the scripts are able to recognize the right paths to the various launcher files.
Some customization of the Newired application is possible. It is recommended to perform any desired customizations before deployment. Customizaion is considered an “advanced topic”. For further information see 7: Advanced Topics.