roadmap/best practice to serve multiple vtours
----------------------------------
I am new to krpano and its tools and have been playing with it for a few days.
What i want to achieve in my web app is to be able to serve virtual tours for each real estate property and somehow automate this prosess.
The MAKE VTOUR (NORMAL) droplet creates a vtour directory in which I guess some of the files may be in common.
panos - property specific
plugins - common
skin - common
tour.html - common
tour.js - common
tour.swf- common
tour.xml - property specific
tour_editor - common
For the common items I want to put them in a seperate static "virtual-tour/commons" folder which will correlate the http://abc.com/virtual-tour/commons route. Like this;
/virtual-tour/commons/
plugins
skin
tour.html
tour.js
tour.swf
tour_editor
For the property specific items I want to put the in a folder unique to that property which will correlate the route http://abc.com/virtual-tour/:propertyId. Like this;
virtual-tour/propertyId/
panos
tour.xml
I also want to automate this property specific process.
Here is the process I constructed so far;
First I created a commons folder on the web server and put the common items mentioned above.
To create a virtual tour for a specific property I follow this steps;
- Run the MAKE VTOUR (NORMAL) droplet in some directory on my computer
- Run tour_editor, add hotspots etc and then save tour.xml
- Edit tour.xml and change
<include url="skin/vtourskin.xml" />
to
<include url="/virtual-tour/commons/skin/vtourskin.xml" />
- Connect with ftp and upload the panos folder and tour.xml to the folder named propertyId on the web server
When i visit http://localhost:8001/virtual-tour/c…xml=/3/tour.xml it works great. (3 in the url is the propertyId)
Thinking lots of properties on the web site,this process is not effective as you can guess.
After reading Config File Reference in the documentation I tried to customize my own droplet by forking the MAKE VTOUR (NORMAL) droplet and related config file. I played with the config file but I could not find an efficient way to automate this process.
For example;
In my config file I set htmltemplate_js=http://localhost:8001/commons/tour.js
I expected that this will replace <script src="[JS]"></script> and produce
<script src="http://localhost:8001/virtual-tour/commons/tour.js"></script>
but it generates
<script src="tour.js"></script>
In the end of the day I got confused.
How can I achieve my goal in all aspects? Is it configuring my own droplet and config file, admin front-end for uploading property specific files? This must be a common problem, what is the roadmap/best practice to serve multiple vtours in my web app?