http://en.wikipedia.org/wiki/Symbolic_link
Basically it is a file that points to another file location. All unix type operating systems use them. A slightly different implementation called a shortcut is used by windows. A symbolic link makes it so you only have to have one file containing data and the symbolic links in other locations point to the file that contains the data.
In ShopSite there are symbolic links in the ss and sc directories that point to files in other locations. Both ss and sc directories have a symlink to the store's auth file in the store's data directory.
The following text box contains a list of the symlinks in the ss and sc directories. Note that sp2 is the storeid for my test store and the ShopSite install directory on the server is /home/jim/10sp2
- Code: Select all
In the sc directory
global.aa -> /home/jim/10sp2/ss/global.aa
libsscommon.so.1 -> /home/jim/10sp2/ss/libsscommon.so.1
localeinfo.dat -> /home/jim/10sp2/ss/localeinfo.dat
sp2.aa -> /home/jim/10sp2/ss/sp2.aa
sp2.auth -> /home/jim/10sp2/data/sp2/sp2.auth
The ss directory has these
certs -> /home/jim/10sp2/sc/certs
libgcc_s.so.1 -> /home/jim/10sp2/sc/libgcc_s.so.1
libpq.so.5 -> /home/jim/10sp2/sc/libpq.so.5
libsqlite.so.0 -> /home/jim/10sp2/sc/libsqlite.so.0
libsqlite3.so.0 -> /home/jim/10sp2/sc/libsqlite3.so.0
sp2.auth -> /home/jim/10sp2/data/sp2/sp2.auth
If these links are not properly in place then ShopSite won't function correctly.
Note: since Windows doesn't truely support symlinks we have had to work around the issue by putting duplicate copies of most of the files that are normally symlinks in the ss and sc directories.
The exceptions on windows are the <storeid>.aa file in the sc directory is the actual file and the ss directory has a special file that we read to get the location of the <storeid>.aa file in the sc directory. Both the ss and sc directories have a special file that we read to get the path to the data directory <storeid>.auth file.