Hi
I seem not to be able to find a way to check a portion of my website which is checked out in my home directory and therefore not reacheable through a webserver.
Any hints?
Thanks
Michele
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could set up a virtual directory to point to the collection of files in your home directory. However, note that this will affect the path to the files.
For instance, suppose your site's homepage was "/index.html". If you had a copy of this file in /home/ravani/work/index.html, you could set a virtual directory for "/" to point to "/home/ravani/work/". But the drawback is that InSite would now look for <STRONG>all</STRONG> files underneath your work directory.
If you're talking about having a collection of files where some are in the Web server's document tree and some are in your working directory, there's no way for InSite to know the difference unless the files in your working directory can be distinguished by their path.
Another thing to note is that if you set up a virtual directory for your working directory and the checked-out documents use relative paths, InSite will expand those paths relative to your working directory, not the directory in the server's document tree.
If you absolutely must check documents outside of the server's tree, your best bet is to check out the <STRONG>entire</STRONG> tree into the working directory. Then set up a single virtual directory to point "/" to your working directory. All URLs will be evaluated relative to that directory.
Hope this helps clarify things a bit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I seem not to be able to find a way to check a portion of my website which is checked out in my home directory and therefore not reacheable through a webserver.
Any hints?
Thanks
Michele
You could set up a virtual directory to point to the collection of files in your home directory. However, note that this will affect the path to the files.
For instance, suppose your site's homepage was "/index.html". If you had a copy of this file in /home/ravani/work/index.html, you could set a virtual directory for "/" to point to "/home/ravani/work/". But the drawback is that InSite would now look for <STRONG>all</STRONG> files underneath your work directory.
If you're talking about having a collection of files where some are in the Web server's document tree and some are in your working directory, there's no way for InSite to know the difference unless the files in your working directory can be distinguished by their path.
Another thing to note is that if you set up a virtual directory for your working directory and the checked-out documents use relative paths, InSite will expand those paths relative to your working directory, not the directory in the server's document tree.
If you absolutely must check documents outside of the server's tree, your best bet is to check out the <STRONG>entire</STRONG> tree into the working directory. Then set up a single virtual directory to point "/" to your working directory. All URLs will be evaluated relative to that directory.
Hope this helps clarify things a bit.