How to change the design

 

1. Create two DNS’ for *.yourdomain and yourdomain to the server hosting the rushfiles system.
(if you have multiple servers, it’s the one with the frontend sites)

2. You will then be able to access the new website on the yourdomain DNS

3. The new website consists of two parts yourdomain/client/ (Company configurator and webclient) and yourdomain/reseller/ (reseller configurator).

4. Go to yourdomain/reseller/ and login.

5. You will start at the tab "My Account" so you will need to go to the tab "Skinning" as shown in the screenshot below. From this tab you are able to click change design. A confirmation popup will be shown and all you need to do now is click yes.  

             



6. This will result in all future calls to the old websites or any unused subdomian will be redirected to this site.
(Note: Do not remove the old DNS’ because there can still be public links and mails pointing to it.)


I am already using the DNS for yourdomain

If you are already using the DNS for yourdomain, we can setup a sub domain for the new webinterface.
For example cloud.rushfiles.com instead of rushfiles.com, but this should be agreed on with your account manager since it’s a manual process.

This cannot be any of the already existing DNS' like webclient.yourdomain, company.yourdomain or reseller.yourdomain.
(Note: this will require we can access your server and do it directly in the database)


I cannot create a *.yourdomain DNS

If you cannot create the *.yourdomain DNS you cannot change the design.


I am using a subdomain for my rushfiles solution.

If you are using a subdomain for your rushfiles solution, you will also need to add a HTTP and HTTPS binding for yourdomain the frontend site in the IIS, here you have to add the certificate covering this address to the HTTPS binging.
For example if I use test.rushfiles.com as my domain, I will need to add a bindings for test.rushfiles.com to the site which starts with frontend in the IIS, and on the HTTPS binding I will need the certificate for *.rushfiles.com because the *.test.rushfiles.com certificate I used under installation, doesn’t cover the address test.rushfiles.com only all sub address of it.