Snug HTTP server - Installation

  • Introduction
    • Introduction
    • Licens agreement
    • Contact information
  • Installation
    • Installing/uninstalling
    • Additional tweaking for BeOS, UNIX and Linux users
  • Configuration
    • The configuration file
    • LogMaxEntries
    • LogMaxAge
    • LogRotation
    • LogDir
    • ExtendedMessages
    • Port
    • Address
    • ExternIP
    • Timeout
    • AddAllowedReferer
    • MaxConnections
    • DirectoryListing
    • ShowProtectedFiles
    • AddIndex
    • AddType
    • AddForbidden
    • AddUser
    • AddVirtual
  • Using the program
    • Versions of Snug HTTP server
    • SnugW16.exe
    • SnugOS2.exe
    • SnugBeOS
    • SnugW32.exe
    • Running the program
    • Troubleshooting
    • URLs and URL encoding
    • Directory listings
  • Compiling
    • BeOS, BeIDE
    • Linux, UNIX, GCC
    • Microsoft Windows, BCC 5.02
    • OS/2, Open Watcom

Installing/uninstalling

This software requires no typical installation you might be used to and does not pollute your system in any way. No directories and no files are created except perhaps for the log files when the server is running. Install the server by decompress the files wherever you want. Reading this you have most likely already done so. The compressed file has subdirectories in it. You must use the "Use folder names" option to restore this directory tree or you will have problems because the files would not be in their proper subdirectories. The server will then be contained within the directory to where you decompressed the files. To summarize the above, you should now have a directory where snug HTTP server is contained. Uninstalling the server is a matter of deleting the directory where you decompressed the files.


Additional tweaking for BeOS, UNIX and Linux users

This section contains notes on using Snug HTTP server on BeOS and other UNIX like operating systems. A few additional things have to be made to get Snug HTTP server working on BeOS, UNIX or Linux.

Step 1. The main configuration file snug.ini is compatible with OS/2 and DOS where each line is terminated with a line-feed/carriage-return combination. This can cause trouble in UNIX, Linux and BeOS. Use the tr command from the terminal in BeOS to fix this. tr -d '\r' < snug.ini > BeOS.ini will create a new file named BeOS.ini. The server should be able to handle both DOS and UNIX style text files. This little trick makes the configuration file more readable in BeOS. We will later use this new file as the main configuration file for the server.

Step 2. SnugBeOS may be unrecognized as an executable on BeOS. This is because the executable flag is lost when copying from one file system to another. If necessary, change the execute permissions on SnugBeOS for users, groups and owners. You can do this in BeOS devEd 1.1 by right-click on SnugBeOS and choose Get Info. Then click on the little arrow near the bottom of the dialog box to get to the permissions. On other UNIX-like systems you may have to do a chmod ugo=x SnugUNIX (or chmod 777 SnugUNIX) before executing the file (where SnugUNIX is the server executable).

BeOS permissions

Changing permissions in BeOS.

If you are using BeOS, treat all references to snug.ini from now on as references to BeOS.ini instead.