Performing a Local Installation of Connect

If you need to host the IBM Aspera Connect Plug-in SDK installers locally, you can download the Connect SDK file and configure Shares to point to a local copy of the Connect SDK hosted at a non-standard location. In this way, your customers can make their users download Connect from a server of their choice.

Create the directory, /opt/aspera/shares/u/connect-sdk, and extract the contents of the connect SDK into this directory.
Change the ownership of the files using the following command:
```
# chown -R nobody:nobody /opt/aspera/shares/u/connect-sdk
```
Skip the next step if you are running Shares 1.9.2 or higher. If you are running a version prior to 1.9.2, you must follow this next step.
Create a Connect Nginx configuration file.
Create a file at /opt/aspera/shares/etc/nginx/locations-available/connect-sdk with the following content:
```
location /connect/ {
  alias /opt/aspera/shares/u/connect-sdk/;
  expires 1d;
}
```

Create a symlink so that Nginx will include the configuration:

# ln -s ../locations-available/connect-sdk /opt/aspera/shares/etc/nginx/locations-enabled

Point Shares to the new Connect SDK location.
Edit the file /opt/aspera/shares/u/shares/app/views/node/shared/_aspera_web_plugin_install.html.haml.
Change the following line to one of the two options below:
```
- connect_autoinstall_location = '//d3gcli72yxqn2z.cloudfront.net/connect/v4'
```
- Option 1:
```
- connect_autoinstall_location = "//#{ request.host_with_port }/connect/v4"
```
- Option 2:
```
- connect_autoinstall_location = '//shares.example.com/connect/v4'
```
  (Where shares.example.com is the FQDN of the Shares server.)

Restart Shares and Nginx.

# service aspera-shares restart

# /opt/aspera/shares/sbin/sv restart nginx

Clear your browser cache.