The ability to run a diverse set of custom add-on applications from backup, security, multimedia, developer tools and many more directly on a Synology NAS makes it extremely versatile and can enable a number of new capabilities within your environment.
While browsing through the packages, I noticed there is a WebStation package which can be used to host a basic website (can also support advanced web applications). This immediately gave me an idea as I can now host my own custom vSphere Content Library, also referred to as a 3rd party content library that are managed outside of vCenter Server, directly on the Synology!
Note: Installing add-on applications will consume additional CPU and memory resources on your Synology, make sure you have enough resources, especially memory before running additional services on your Synology.
- An already created 3rd party content library that is ready to be hosted
- To learn more about what and how to create your own 3rd party content library, please refer to this blog post for more details.
Step 1 - Login to the Synology DiskStation Manager (DSM) and open up the Package Center on the desktop. Search for the Web Station application and initiate the installation.
Step 3 - Finally, from the DSM desktop, navigate to File Station and you should now see a new directory called web, which is the root directory of your web server. You can now create a new folder that will house one of your 3rd party content libraries. In my example, I have a 3rd party content library that contains all of my Nested ESXi Virtual Appliances and I have named the folder nested-esxi.
Step 4 - You can upload the directory structure of your 3rd party content library using the File Station, but I found this to be really inefficient because it can not upload folders directly and I have a lot of directories and files to upload.
Instead, I opted for using SCP command-line utility which will require you to enable SSH access on the Synology by going to Control Panel->Security->Terminal & SNMP and selecting the Enable SSH Service and click on the apply button for change to go into effect.
If you are on macOS, I found out the hard way that the SCP utility actually defaults to the SFTP protocol rather than SSH, which I thought was quite strange. In any case, it considers the SCP protocol as legacy ... After a bit of searching online, I found that you can enable the "legacy" SCP option by simply passing in the -O option to the command line and now you can easily transfer your entire 3rd party content library directory structure to the Synology.
Here is an example SCP command where I am already in the root folder of my locally created 3rd party content library and I want to recursively transfer all files to my nested-esxi directory is located under /volume1/web, where volume1 is the label of your Synology volume.
scp -O -r * admin[at]nas.primp-industries[dot]local:/volume1/web/nested-esxi/
To verify that everything has been configured correctly, you should be able to access one of your files such as the 3rd party content library lib.json by opening a browser to the following URL (replace with your own values):
If that opened up successfully, we are now ready to consume our 3rd party content library by creating a new subscribed library as shown in the screenshot below and providing the URL which will be https://nas.primp-industries.local/nested-esxi/lib.json (replace with your own values)