Hello, your wiki says:

SuperContainer for hosting providers

You can run SuperContainer version 1.72 or later for your clients in Tomcat by following these steps:

• Each client will need to purchase a separate license of SuperContainer, or you may purchase a license for them.
  
• Modify SuperContainer/WEB-INF/web.xml file and put in valid values for the 'activationCode' and 'registeredTo' settings for your client.
  
• Change the name of the SuperContainer folder to that client's name and put it into the webapps folder. The URL will become whatever you name the folder, so if you change the folder name from 'SuperContainer' to 'ClientX', the URL to access SuperContainer will be http://yourServer:8080/ClientX/Files.
  

I'm just looking to deploy on our own server. We're running SC standalone. On a Mac OS X server, where should the SuperContainer.jar and SuperContainer folders live, so that we can change the name of the folder to 'project x' instead of supercontainer?

Many thanks!

Michael Ashley

Michael--

You can place the downloaded SuperContainer folders virtually anywhere on the hard drive, so long as the files stay together and are not renamed. You can create a parent folder however, "Project X" for example, and place the SuperContainer directory within that folder.

Hope this helps,

Thank you Obinna. So we can close this ticket, and just to let the community know, a reminder that there are several ways to install and configure SuperContainer. in order to take advantage of the CoreImage rendering on our Mac server, we are running SuperContainer standalone, not as a web service in Tomcat. According to Obinna, the SuperContainer folder path is hardcoded, so cannot be changed. The only way to change it is to run SuperContainer as a service.

We are weighing our options and doing some more tests to see if it's worth giving up the rendering of PDF previews and Photoshop docs in order to have a different URL.

Thanks!