A First Glimpse

This tutorial assumes, you are working with the SDK. If you have a different setup, local paths and URLs may vary.

Change into the directory of the example site and have a look at the files:

$ cd ~/fit14-devbox/projects/_default/sites/_default/
$ find

Sites are grouped together in projects, which in turn are stored in the projects folder. A FIT site consists of two parts: We have configuration data in conf and document data in public. The configuration determines how the site should behave, which backend servers to talk to, how to rewrite URLs and so on. Document data is static, local content which is mostly useful for error pages or prototyping.

The URL map in conf/urlmap.xml defines the routing of incoming URLs to backend sources. In our example we get the content from the local file system. We use the FIT-internal fit:// protocol (speak “FIDJ”) to address the public/ directory where our documents live. (You will learn more about fit:// URLs later on).

<urlmap mandatory="true">
  <map path="/" source="fit://site/public/"/>
</urlmap>

The public directory contains a simple HTML document index.html. Accessing files in the public folder resembles requesting a simple HTTP file server:

  • Files are delivered with status code 200 and a HTTP Content-Type header corresponding to the file extension.
  • Non-existing files will result in a 404 response without a body.
  • A directory request (e.g. fit://site/public/) returns a 403 error, unless…
  • … an index file named index.html or index.xml exists in the directory. If it can be read, it will be served with status code 200.

Enough theory! Open your browser, point it to the domain of your FIT server and enjoy:

http://local14.sevenval-fit.com/

Look how the Adaptation Instructions contained in the HTML in public/index.html are modifying the output.

Next Step