On 29/08/12 21:07, Martijn Coppoolse wrote:
Stuart Rackham <srackham@...> writes:
I'm displaying documentation using the Embedded Documentation feature,
the web server returns the contents of symlinks, is there a way to
make the web server follow symlinks?
What is the value of the "allow-symlinks" setting?
From the help:
allow-symlinks If enabled, don't follow symlinks, and instead treat
(versionable) them as symlinks on Unix. Has no effect on Windows
(existing links in repository created on Unix become
plain-text files with link destination path inside).
Default: off
IIRC, this would suggest that allow-symlinks is ON in your repository. This
means that the target of the symlink won't present in the repository. And since
—AFAIK— Fossil's web server only serves files from inside the repository, it
won't serve files behind a symlink.
Yes, the "allow-symlinks" setting is on, in this particular repository
there are shared resources (CSS files and images) that are common to
separate HTML document directories. The separate document directories
refer to common image directories and CSS files through relative
symlinks. Both the symlinks and their target files are in the project
repository. I was assuming that the web server would see the file was
a symlink and load the actual file artifact that it refered to. This
is what you expect when you read a file via a symlink and is how a web
server would treat the file if it resided on a file system.
Cheers, Stuart
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
