Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://wiki.cs.msu.ru/System/InstallationGuidePart2?cover=print;rev=1
Дата изменения: Unknown Дата индексирования: Mon Apr 11 17:03:33 2016 Кодировка: |
System.Skins
refers to the Skins
topic in your System web. To go directly to a topic, enter the full topic name, such as System.Skins
, into the "Jump" text box at the top right of any Foswiki page.
To make it easier to follow the instructions in this section, you can view this installation guide using your Foswiki site by entering System.InstallationGuide
into the "Jump" text box. By doing this instead of using the INSTALL.html
file from the distribution, you will be able to use the embedded hyperlinks to jump directly to the referenced pages.
All of the Foswiki documentation can also be found online in the Foswiki documentation section (the "System" web) of the Foswiki web site.
Note the configure
page mentioned in this section is accessed by visiting http://wiki.cs.msu.ru/bin/configure
your web browser.
Main.SitePreferences
. If a given preference is not set in Main.SitePreferences
, then a default value is picked up from System.DefaultPreferences
, if present, or, for extensions, from the extension topics.
To simplify your upgrades, do not modify System.DefaultPreferences
. Instead, copy any settings you want to change from System.DefaultPreferences
to Main.SitePreferences
.
To see the available preferences that can be set, look through System.DefaultPreferences
.
If, for some reason, you wish to pick up default preferences from a different topic, you can set the location in the Miscellaneous settings
pane of the configure
page, in the {SitePrefsTopicName}
setting (visible when Expert mode is enabled). It is recommended that you leave this setting to its default value, DefaultPreferences
.
Foswiki has a many security features that can be enabled/disabled and adjusted to suit your needs.
In many cases enabling a security feature prevents other features. It is a balance that the administrator has to choose depending on the purpose of the Foswiki installation (confidential vs public knowledge), the type of installation (intranet vs internet), and your type of business.
A new administrator is encouraged to read Foswiki:Support.SecurityFeatures which gives a walkthrough of the different security aspects and how to set the appropriate configuration settings. Note that that some security settings are only visible in configure in "expert mode" which you enter by clicking the "Yes, I've read all the documentation" button at the top of the configure screen.configure
page.
tools/mailnotify
script, as described in the System.MailerContrib topic.
{WebMasterEmail}
email account. Obtain these as you would for any other S/MIME e-mail user.
To enable Foswiki to sign administrative e-mails: Crypt::SMIME
installed.
/etc/pki/tls/certs
configure
script, change the following settings under Mail and Proxies: {MailMethod}
and {MailProgram}
to enable an external mail program such as sendmail. Net::SMTP
is not supported. {SMTP}{MAILHOST}
, {SMTP}{SENDERHOST}
, {SMTP}{Username}
and {SMTP}{Password}
are not used an may be deleted.
SMTPMAILHOST
is defined in Main.SitePreferences
it should be removed.
{SmimeCertificateFile}
configuration variable
{SmimeKeyFile}
configuration variable
configure
script an resolve any errors that it identifies
All out-going administrative e-mails will now be signed.
tools/tick_foswiki.pl
script, and set a negative value on the configure
page for {Sessions}{ExpireAfter}
. For more details, read System.CommandAndCGIScripts#tick_foswiki_pl.
Localisation
section of the configure
page. For more information, see Foswiki:Support.InternationalizationSupplement.
If you are not using Foswiki to manage your users' passwords or email addresses, or would just like to enhance the default pages, then modify the following topics accordingly with information appropriate for your site:
ALLOWTOPICCHANGE
preference setting to Main.NewUserTemplate so only the user can edit their own user topic. In particular, on a public Foswiki site, restricting edit access will avoid vandalism and spam.
The top bar and bottom bar are common across all webs.
To customize the top bar, copy System.WebTopBarExample to WebTopBar, and make your desired changes to WebTopBar. To customize the bottom bar, copy System.WebBottomBarExample to WebBottomBar, and make your desired changes to WebBottomBar. The side bar can be customized on a per web basis. To customize the side bar, copy the WebLeftBarExample topic in the given web to WebLeftBar, and make your desired changes to WebLeftBar. If you would like to move the side bar to the right of the page, see System.PatternSkin for more details.WEBCOPYRIGHT
preference. Its default is the following: Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
If your Foswiki site is used in an environment without public access you should replace this with your normal copyright notice. You should also consider adding a security classification (e.g., For Internal Use Only) so people do not have to add this manually to every new topic.
If your Foswiki site is publicly accessible, you need to decide which copyright and license you wish to apply to all contributions. For open source applications, licenses such as the GNU Free Documentation License, FreeBSD Documentation License, and one of the various Creative Commons licenses are possible licenses to consider. Remember that once people have started contributing, you cannot retroactively change the license (unless it has a provision for this).To change the copyright statement, perform the following steps:
WEBCOPYRIGHT
preference setting from System.DefaultPreferences to Main.SitePreferences
. Change the value to your desired text. This value will be your new default across all webs.
WEBCOPYRIGHT
preference in the WebPreferences
topic for the given web. For example, you could add a confidential classification to a web that has restricted access.
WEBCOPYRIGHT
preference setting in System.WebPreferences covers the documentation that comes with Foswiki, and should not be changed.
tools/extension_installer
.deb
packages should only use the debian tools when installing extensions.
The simplest way is to visit configure:Extensions. Use the Find More Extensions button to download and install additional extensions from the foswiki.org website. If you are behind a firewall or your server has no access to the Internet, you can also install plugins manually. Installation instructions for each plugin are located in its corresponding topic on http://foswiki.org/. Additional documentation on Foswiki plugins can be found at Foswiki:Support.PluginsSupplement.
When installing an extension from the configure
interface: working/configure/backup
directory
!noci
, disabling checkin, they will still be checked in if existing revision control files are found, suggesting that local modifications have occurred.
_installer
package must be run from the root directory of the Foswiki installation.
_installer
module must be downloaded from the Extension repository. The extension archive will be downloaded if required.
_installer
is run, it will install the Extension and dependencies similar to the configure
interface except: _installer
module is saved in working/configure/pkgdata
working/logs/configure/[NameOfExtension]-yyyymmdd-hhmmss-[Action].log
configure
page. In addition, some extensions also require configuration in this section.
The instructions for using the extensions installer from the shell are
retrieved by using the "usage" command: tools/extension_installer usage
or
./SomePlugin_installer usage
perl working/configure/pkgdata/X509UserPlugin_installer usage Usage as a custom installer: X509UserPlugin_installer -a -n -d -r -u -c install X509UserPlugin_installer -a -n uninstall X509UserPlugin_installer manifest X509UserPlugin_installer dependencies Usage as a generic installer: tools/extension_installer X509UserPlugin -a -n -d -r -u -c install tools/extension_installer X509UserPlugin -a -n uninstall tools/extension_installer X509UserPlugin manifest tools/extension_installer X509UserPlugin dependencies If command (install, uninstall ..) is not provided, default is to install the extension. Operates on the directory tree below where it is run from, so should be run from the top level of your Foswiki installation. Depending upon your installation, you may need to execute perl directly perl tools/extension_installer ... or perl X509UserPlugin_installer ... "install" will check dependencies and perform any required post-install steps. "uninstall" will remove all files that were installed for X509UserPlugin even if they have been locally modified. -a means don't prompt for confirmation before resolving dependencies -d means auto-download if -a (no effect if not -a) -r means reuse packages on disc if -a (no effect if not -a) -u means the archive has already been downloaded and unpacked -n means don't write any files into my current install, just tell me what you would have done -c means don't try to use CPAN to install missing libraries "manifest" will generate a list of the files in the package on standard output. The list is generated in the same format as the MANIFEST files used by BuildContrib. "dependencies" will generate a list of dependencies on standard output.
Caution: When removing an extension, no dependency checking is performed.The web and command line interfaces can be used to uninstall extensions. When an extension is remove, the following occurs:
- Dependencies are not removed
- Other Extensions dependent on the removed extension may become non-operational.
_installer
package is used to recover the manifest. If it cannot be found locally, it will be downloaded from the configured extension repository
configure/working/backup
directory _uninstaller
was required, the backup will be made per the current installer's manifest. It is preferable to always save the _installer
modules.
,v
revision control files will be removed, including the _installer
. working/logs/configure/[NameOfExtension]-yyyymmdd-hhmmss-[Action].log
working/configure/pkgdata/SomeExtension_installer uninstall
unzip
or tar -xzf
of the backup file should be all that is required:
cd /root/of/foswiki tar -zxvf * working/configure/backup/[Extension}-backup-[yyyymmdd]-[hhmmss].tgz # or unzip working/configure/backup/[Extension}-backup-[yyyymmdd]-[hhmmss].zip
TWikiCompatibilityPlugin
. This plugin enables most TWiki extensions to work with Foswiki, without modifications. It also maps requests for legacy TWiki web topics to their Foswiki equivalents, as defined in Foswiki:Development.TopicNameMappingTable. The TWIKIWEB
and MAINWEB
TWiki variables are also mapped to the new Foswiki macros SYSTEMWEB
and USERSWEB
.
If you are not upgrading an existing TWiki installation and do not plan to install plugins from the TWiki web site, it is recommended that you disable the TWikiCompatibilityPlugin in the Plugins Section on the configure
page.
If a plugin exists both in a TWiki version and a Foswiki version, it is strongly recommended that you use the Foswiki version, as this is coded to work optimally with Foswiki. As part of the Foswiki project, the Foswiki community is evaluating all of the extensions that are available for TWiki, and porting them over to the Foswiki name space. Many of them are being enhanced through the removal of bugs and security vulnerabilities, resulting in better, more functional extensions for Foswiki.
Fast CGI | FastCGIEngineContrib | Supports the mod_fastcgi and mod_fcgid extensions |
mod_perl | ModPerlEngineContrib | supports the apache mod_perl extension |