home > explanation

explanation

Created by mfranken. Last edited by mfranken, 3 years and 137 days ago. Viewed 6,793 times. #28

[diff] [history] [edit] [rdf]

labels

attachments

Mapping your collection behind a Webserver

Define a collection called 'My Documents' that sits in e:\docs. The index will be created in d:\temp\zilverline\index\My Documents.

All documents in zip, rar and chm are kept on disk, and stored in the cache that sits in d:\temp\zilverline\cache\My Documents.

collectiondetails

The URL will be used in the search results. Instead of pointing back to the original location (e:\docs) it will point at http://localhost/books_e/docs/ (which should exist on your server, and should be mapped to e:\docs). You can do this by specifying an alias e.g. in Apache:

Alias /books_e/docs "e:/docs"
	<Directory "e:/docs">
		Options FollowSymLinks Indexes
		IndexOptions NameWidth=*
		AuthType Digest
		AuthName "private"
		AuthDigestFile conf/passwd/digests
		AuthDigestDomain /tech
		Require valid-user
	</Directory>

Since you specify a cacheURL, the cache can be mapped to sit behind the webserver at http://localhost/cachedBooks/docs/. You can create this mapping again as follows:

Alias /cachedBooks "D:/temp/zilverline/cache"
	<Directory "D:/temp/zilverline/cache">
		Options FollowSymLinks Indexes
		IndexOptions NameWidth=*
		AuthType Digest
		AuthName "private"
		AuthDigestFile conf/passwd/digests
		AuthDigestDomain /tech
		Require valid-user
	</Directory>

no comments | post comment

see also:
installation	Quick start	screenshot	Collections
faq	snipsnap-search	snipsnap-index	Extractors
Getting Zilverline	Analyzer	Handling Archives	Boostfactors
start	snipsnap-notfound	apidocs	Source Code
scheduling	mfranken	snipsnap-portlet-1	command-line indexer

Sun	Mon	Tue	Wed	Thu	Fri	Sat
					1	2
3	4	5	6	7	8	9
10	11	12	13	14	15	16
17	18	19	20	21	22	23
24	25	26	27	28	29	30
31

explanation

Mapping your collection behind a Webserver

News

Get Zilverline

Source

Build Information

Installation

Screenshot

FAQ