46
Developers / Exporting Device Templates - ignoring sqlCVS for the moment
« on: September 24, 2008, 01:21:52 pm »
Hi,
usually, the course of action with LinuxMCE is, to utilize sqlCVS to commit a new device template for anyone to use it. Unfortunately, anonymous commits to sqlCVS have caused myself problems in the past. I had a need to export created device templates, to import those devices into a new LinuxMCE installation.
I created a small script called DeviceTemplate2php. This script can be called from a html page, and creates a new php file called device####.php, where #### is replaced with the original device template ID.
The small script is located at http://possy.de/DeviceTemplate2php.tar.gz and should be stored on the LinuxMCE core in /var/www/ under the name DeviceTemplate2php.php. Now you can execute the file from your browser by using the url
http://dcerouter/DeviceTemplate2php.php?DeviceTemplateID=1933
in case you want to export your device template 1933.
Please try it out, and let me know any problems you might experience.
rgds
Oliver
usually, the course of action with LinuxMCE is, to utilize sqlCVS to commit a new device template for anyone to use it. Unfortunately, anonymous commits to sqlCVS have caused myself problems in the past. I had a need to export created device templates, to import those devices into a new LinuxMCE installation.
I created a small script called DeviceTemplate2php. This script can be called from a html page, and creates a new php file called device####.php, where #### is replaced with the original device template ID.
The small script is located at http://possy.de/DeviceTemplate2php.tar.gz and should be stored on the LinuxMCE core in /var/www/ under the name DeviceTemplate2php.php. Now you can execute the file from your browser by using the url
http://dcerouter/DeviceTemplate2php.php?DeviceTemplateID=1933
in case you want to export your device template 1933.
Please try it out, and let me know any problems you might experience.
rgds
Oliver