====Deploying Scripts to your Server====

If your script is looking good and you'd like to make it publically available, you can upload it to ARDI. If you haven't already tested it, we suggest first doing your development and testing locally - see [[ardiscript:running_and_debugging_local_scripts]].

This will make the script available in the "Playback" tab of ARDI-VE.

To deploy your script, you need to upload it. Follow the steps below...

   * Rename your file - change the extension from **xml** to **script**.
   * In the ARDI web interface, search for the environment you would like the script to appear in.
   * Open the details of the asset.
   * Go to the 'Media' tab
   * Upload the script file.

Now the script is uploaded and publicly available.

If your script also contains media content, you'll need to upload that too. To upload script-based media, you can....

   * Go to 'Effects, Options and Scripts' for the environment.
   * Select your script from the list.

{{:ardiscript:scriptlist.png?400|}}

   * Use the upload controls on the right (or the bottom on very small screens) to upload your media.
  
{{:ardiscript:scriptediting.png?400|}}

===Check Your Media Paths===

//This section only applies if your script includes media files//

If you followed the instructions on [[ardiscript:running_and_debugging_local_scripts]], you hopefully created a folder to store all your scripts media.

If you did not, you may need to update the paths to your media.

So that you don't get issues with different scripts having conflicting file names, ARDI places the media for each script into a separate folder. A file called //photo.jpg// for the //Introduction// script will be placed in **Introduction/photo.jpg**.

So a line in your script that used to say...

<code>
<viewmedia media="photo.jpg"/>
</code>

...might need to be updated to say...

<code>
<viewmedia media="Introduction/photo.jpg"/>
</code>

If your media references in your script don't already use a folder, you should update them.