UPGRADING\r
---------\r
It is always a good idea to make copies of your current FMS installation before\r
-continuing. First shut down FMS and then replace the binary and template.htm\r
-with those from the new version. You may keep the same database unless\r
-otherwise noted.\r
+continuing. First shut down FMS and then replace the binary and templates with\r
+those from the new version. You may keep the same database unless otherwise\r
+noted.\r
\r
INSTALLATION\r
------------\r
-Place the binary and template.htm in a directory of your choice. On the first\r
+Place the binary and any templates in a directory of your choice. On the first\r
run, a database file will also be created in this directory. Make sure the\r
user that runs FMS has read/write access to this directory.\r
\r
directory as the fms binary. In the template, the string [LINKS] will be\r
replaced by a <ul> list of links and [CONTENT] will be replaced by the page\r
content. The Freesite will be inserted once a day and contain your last 10\r
-posts and your trust list if you are publishing it.\r
+posts and your trust list if you are publishing it. The site will be inserted\r
+to a USK accessible via: USK@yourpublickey.../fms/0/\r
\r
TRUST\r
-----\r
\r
A note on NULL trust: If you neither trust or distrust an identity, they will\r
have NULL trust (no trust at all). You will download messages and trust lists\r
-from identities with NULL peer trust as long as the local trust level is above\r
-your configured minimum. You will also download messages from identities with\r
-NULL local message trust (the peer message trust must be NULL or > your\r
+from identities with NULL peer trust as long as the local trust level is at or\r
+above your configured minimum. You will also download messages from identities\r
+with NULL local message trust (the peer message trust must be NULL or >= your\r
configured minimum as well), but you will not download trust lists from\r
identities with NULL local trust list trust.\r
projects / fms.git / blobdiff