Server Paths, Aliases and Templates

When running Alkaline, it is possible to specify multiple paths containing different asearch.cnf files. For example:

./asearch 9999 foo bar

will load both configurations and indexes from foo/asearch.cnf and bar/asearch.cnf. Each path, such as foo is called an alias, since it defines a particular configuration. It must contain an asearch.cnf file.

Each path can contain templates in a form of html files with specific Alkaline tags. To specify a remote file, you must create a file with a .aln extension containing the url to query on a single line.

For example, the directory foo can contain a file called search.html containing the search box and Alkaline tags for mapping search results. To search the foo index, navigate to http://server:port/foo/search.html .

If the search.html template is in fact at http://www.bar.com/search.html, a file called search.aln can be created in the directory foo with a single line in it:

http://www.bar.com/search.html

To search the foo index and display results using this template, navigate to http://server:port/foo/search.aln .