COMPILING --------- Compiling FMS requires CMake, Poco ( version >=1.2.9 ) and iconv if you want to do charset conversion. Other required libraries are bundled with FMS. To compile, run these commands from the source directory: cmake -D I_HAVE_READ_THE_README=ON . make If you want to use the bundled SQLite3 library, add a -D USE_BUNDLED_SQLITE=ON to the cmake command. Use of the bundled SQLite3 library is on by default when compiling on a Mac. To turn off charset conversion to UTF-8 when sending messages, add a -D DO_CHARSET_CONVERSION=OFF. Compiling with charset conversion turned on is recommended. UPGRADING --------- It is always a good idea to make a copy of your current FMS installation before continuing. First shut down FMS, make a copy of the directory, and then replace all files except the database with those from the new version. You may keep the same database unless otherwise noted. INSTALLATION ------------ Place the binary and any templates in a directory of your choice. Windows users may need to download the runtime DLLs available from the fms Freesite and place in the fms directory if they are not already installed on the system. On the first run, a database file will also be created in this directory. Make sure the user that runs FMS has read/write access to this directory. RUNNING ------- You may run FMS in console mode by running the binary directly. You can view available command line options by typing /help on Windows and --help on other platforms. If you are running *nix and would like to run as a daemon, use the --daemon argument. On Windows, /registerService will install FMS as a service, and /unregisterService will uninstall the service. Use the /displayName=name argument when installing the service to set the service name to whatever you want. You will need to manually start the service unless you change the startup type in the service properties. EXITING ------- To exit FMS running in console mode, press CTRL+C while at the console. You can also use the shutdown button on the web interface to close FMS. As a last resort, you may kill the process. WEB INTERFACE ------------- By default, a web interface for administration will be running at http:// localhost:8080. You can use the interface to configure and administer FMS. NNTP CONFIGURATION ------------------ By default, the NNTP server will listen on port 1119. Configure your newsreader to connect to the machine running FMS on this port. Use the web interface to create an identity and use the name of the identity as the username for the newsgroup account. The email address may be anything, as it is discarded when posting messages. POSTING MESSAGES ---------------- You must set your newsreader to use UTF-8 when posting messages. Any non-text attachment to the message will be inserted as a regular file and the key added to the body of the message when received. Keep the attachments small, as the message can't be inserted until all attachments are inserted. Text attachments will be inlined with the message body. Cross posting is fine, but remember that each identity can set a limit to the number of boards each message may be cross posted to. CONTROL BOARDS -------------- Control boards are special boards that will add/remove trust from an identity. Create control boards in the web interface, and then reply to an identity's message to a control board to change the trust of the identity as per the settings for the board. You may cross post to a regular board and a control board with the same message. The control boards will be stripped from the message before inserting into Freenet. FREESITES --------- Each identity has the option to publish a freesite. A generic HTML template called site-template.htm is used to insert the site. You can customize the template by placing an HTML file called identityname-template.htm in the same directory as the fms binary. In the template, the string [LINKS] will be replaced by a