Changes between Version 4 and Version 5 of TracInstall


Ignore:
Timestamp:
25/03/2015 10:37:46 (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracInstall

    v4 v5  
    1 {{{#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc; text-align: center"
    2 
    3  '''NOTE: the information in this page applies to Trac 1.0, the current version of Trac. \\
    4  For installing previous Trac versions, please refer to [[wiki:0.12/TracInstall]] (for Trac 0.12)'''
    5 }}}
    6 
    71= Trac Installation Guide for 1.0
    82[[TracGuideToc]]
     
    104Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.
    115
    12 Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version, as usual.
    13 
    14 If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
    15 
    16 What follows are generic instructions for installing and setting up Trac and its requirements. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please be sure to '''first read through these general instructions''' to get a good understanding of the tasks involved.
     6Since version 0.12, Trac can also be localized, and there is probably a translation available in your language. If you want to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version.
     7
     8If you're interested in contributing new translations for other languages or enhancing the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
     9
     10What follows are generic instructions for installing and setting up Trac. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please '''first read through these general instructions''' to get a good understanding of the tasks involved.
    1711
    1812[[PageOutline(2-3,Installation Steps,inline)]]
     
    2418 * [http://www.python.org/ Python], version >= 2.5 and < 3.0
    2519   (note that we dropped the support for Python 2.4 in this release)
    26  * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6
     20 * [http://pypi.python.org/pypi/setuptools setuptools], version >= 0.6
    2721 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6
    2822
    29 You also need a database system and the corresponding python bindings.
    30 The database can be either SQLite, PostgreSQL or MySQL.
     23You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL.
    3124
    3225==== For the SQLite database #ForSQLite
    3326
    34 As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).
    35 
    36 However, if you'd like, you can download the latest and greatest version of [[trac:PySqlite]] from
    37 [http://code.google.com/p/pysqlite/downloads/list google code], where you'll find the Windows
    38 installers or the `tar.gz` archive for building from source:
    39 {{{#!sh
    40 $ tar xvfz <version>.tar.gz
    41 $ cd <version>
    42 $ python setup.py build_static install
    43 }}}
    44  
    45 This will download the latest SQLite code and build the bindings.
    46 
    47 SQLite 2.x is no longer supported.
    48 
    49 A known bug in PySqlite versions 2.5.2-4 prohibits upgrades of Trac databases
    50 from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
    51 older. See #9434 for more detail.
    52 
    53 See additional information in [trac:PySqlite PySqlite].
     27As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python: the `sqlite3` module.
     28
     29Optionally, you may install a newer version of [pypi:pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.
    5430
    5531==== For the PostgreSQL database #ForPostgreSQL
     
    6137See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
    6238
    63 
    6439==== For the MySQL database #ForMySQL
    6540
    66 Trac can now work quite well with MySQL, provided you follow the guidelines.
     41Trac works well with MySQL, provided you follow the guidelines:
    6742
    6843 * [http://mysql.com/ MySQL], version 5.0 or later
    6944 * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later
    7045
    71 It is '''very''' important to read carefully the [trac:MySqlDb] page before creating the database.
     46Given the caveats and known issues surrounding MySQL, read carefully the [trac:MySqlDb] page before creating the database.
    7247
    7348=== Optional Dependencies
     
    7651
    7752===== Subversion
    78  * [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
    79 
    80 There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. TracSubversion points you to [http://alagazam.net Algazam], which works for me under Python 2.6.)
     53 * [http://subversion.apache.org/ Subversion], 1.5.x or later and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. may still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
     54
     55There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. [trac:TracSubversion] points you to [http://alagazam.net Alagazam], which works for me under Python 2.6.)
    8156
    8257Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings.
    8358
    84 
    8559'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
    8660
     61===== Git
     62 * [http://git-scm.com/ Git] 1.5.6 or later.
     63
     64More information is available on the [trac:TracGit] page.
    8765
    8866===== Others
    8967
    90 Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].
     68Support for other version control systems is provided via third-parties. See [trac:PluginList#VersionControlSystems] and [trac:VersionControlSystem].
    9169
    9270==== Web Server
    9371A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below.
    9472
    95 Alternatively you can configure Trac to run in any of the following environments.
     73Alternatively you can configure Trac to run in any of the following environments:
    9674 * [http://httpd.apache.org/ Apache] with
    9775   - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and
    9876     http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
    99    - [http://modpython.org/ mod_python 3.3.1], (deprecated: see TracModPython)
     77   - [http://modpython.org/ mod_python 3.5.0], see TracModPython
    10078 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
    10179 * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
    10280   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
     81 * a FastCGI and FastCGI-to-WSGI gateway (see [trac:TracOnWindowsIisWfastcgi])
    10382 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
    10483   is highly discouraged''', better use one of the previous options.
     
    10786==== Other Python Packages
    10887
    109  * [http://babel.edgewall.org Babel], version >= 0.9.5,
    110    needed for localization support (unreleased version 1.0dev should work as well)
     88 * [http://babel.edgewall.org Babel], version 0.9.5, 0.9.6 or >= 1.3
     89   needed for localization support
    11190 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
    11291   for WikiRestructuredText.
    11392 * [http://pygments.org Pygments] for
    114    [wiki:TracSyntaxColoring syntax highlighting].
     93   [TracSyntaxColoring syntax highlighting].
    11594   [http://silvercity.sourceforge.net/ SilverCity] and/or
    11695   [http://gnu.org/software/enscript/enscript.html Enscript] may still be used
     
    12099   an internal time zone implementation.
    121100
    122 '''Attention''': The various available versions of these dependencies are not necessarily interchangeable, so please pay attention to the version numbers above. If you are having trouble getting Trac to work please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].
    123 
    124 Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing'' (there are even some pages that are still talking about Trac 0.8!).
    125 
     101{{{#!div style="border: 1pt dotted; margin: 1em"
     102**Attention**: The available versions of these dependencies are not necessarily interchangeable, so please pay attention to the version numbers. If you are having trouble getting Trac to work, please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].
     103}}}
     104
     105Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing''.
    126106
    127107== Installing Trac
     108
     109The [TracAdmin trac-admin] command-line tool, used to create and maintain [TracEnvironment project environments], as well as the [TracStandalone tracd] standalone server are installed along with Trac. There are several methods for installing Trac.
     110
    128111=== Using `easy_install`
    129 One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools].
    130 With setuptools you can install Trac from the Subversion repository;
     112Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].
    131113
    132114A few examples:
     
    143125   either use a released version or install from source
    144126
     127More information can be found on the [trac:setuptools] page.
     128
    145129{{{#!div style="border: 1pt dotted; margin: 1em"
    146130**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in the sections on [#RunningtheStandaloneServer Running The Standalone Server] and [#RunningTraconaWebServer Running Trac on a Web Server].
     
    165149Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings.
    166150
    167 pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on pypi.python.org and create a self contained installation in `/opt/user/trac`.
     151pip will automatically resolve all dependencies (like Genshi, pygments, etc.), download the latest packages from pypi.python.org and create a self contained installation in `/opt/user/trac`.
    168152
    169153All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive)
    170154
    171 Additionally, you can install several Trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.
    172 
    173 
     155Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip.
    174156
    175157=== From source
    176 Of course, using the python-typical setup at the top of the source directory also works.
    177 
    178 You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`), or you can get the source directly from the repository (see [trac:SubversionRepository] for details).
     158Using the python-typical setup at the top of the source directory also works. You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`) from the [trac:TracDownload] page, or you can get the source directly from the repository. See [trac:TracRepositories#OfficialSubversionrepository TracRepositories] for details.
    179159
    180160{{{#!sh
     
    182162}}}
    183163
    184 ''You'll need root permissions or equivalent for this step.''
     164''You will need root permissions or equivalent for this step.''
    185165
    186166This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory
    187167of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`.
    188168
    189 The script will also install the [wiki:TracAdmin trac-admin] command-line tool, used to create and maintain [wiki:TracEnvironment project environments], as well as the [wiki:TracStandalone tracd] standalone server.
    190 
    191169If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
    192170{{{#!sh
     
    195173Alternatively, you can run `bdist_egg` and copy the .egg from `dist/` to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
    196174
    197 === Advanced Options
     175=== Using installer
     176
     177On Windows Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32 and 64 bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation.
     178
     179=== Using package manager
     180
     181Trac may be available in the package repository for your platform. Note however, that the version provided by the package manager may not be the latest release.
     182
     183=== Advanced `easy_install` Options
    198184
    199185To install Trac to a custom location, or find out about other advanced installation options, run:
     
    212198easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
    213199}}}
    214 Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default.
     200Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.5/site-packages }}} by default.
    215201
    216202The above will place your `tracd` and `trac-admin` commands into `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.5/site-packages`, which is Apple's preferred location for third-party Python application installations.
    217203
    218 
    219204== Creating a Project Environment
    220205
    221 A [TracEnvironment Trac environment] is the backend storage where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable [TracIni configuration file], and various other files and directories.
    222 
    223 A new environment is created using [wiki:TracAdmin trac-admin]:
     206A [TracEnvironment Trac environment] is the backend where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable [TracIni configuration file], and other files and directories.
     207
     208A new environment is created using [TracAdmin trac-admin]:
    224209{{{#!sh
    225210$ trac-admin /path/to/myproject initenv
     
    229214
    230215Using the default database connection string in particular will always work as long as you have SQLite installed.
    231 For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
     216For the other [trac:DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
    232217
    233218Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterwards, and support for specific version control systems is disabled by default.
     
    235220Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
    236221
    237 When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2 (though the best advice is to opt for a platform with sub-second timestamp resolution when possible regardless of the version of Trac you are running).
     222{{{#!div style="border: 1pt dotted; margin: 1em"
     223**Filesystem Warning:** When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2. The best advice is to opt for a platform with sub-second timestamp resolution, regardless of the Trac version.
     224}}}
    238225
    239226Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
     
    248235}}}
    249236
    250 
    251237== Deploying Trac
    252238
    253239=== Running the Standalone Server
    254240
    255 After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
     241After having created a Trac environment, you can easily try the web interface by running the standalone server [TracStandalone tracd]:
    256242{{{#!sh
    257243$ tracd --port 8000 /path/to/myproject
     
    280266
    281267Trac provides various options for connecting to a "real" web server:
    282  - [wiki:TracFastCgi FastCGI]
     268 - [TracFastCgi FastCGI]
    283269 - [wiki:TracModWSGI mod_wsgi]
    284  - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)//
    285  - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)//
     270 - [TracModPython mod_python]
     271 - //[TracCgi CGI] (should not be used, as the performance is far from optimal)//
    286272
    287273Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.
     
    289275==== Generating the Trac cgi-bin directory #cgi-bin
    290276
    291 In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].
    292 
    293 There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
     277In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [TracAdmin trac-admin].
     278
     279There is, however, a bit of a chicken-and-egg problem. The [TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
    294280{{{#!sh
    295281mkdir -p /usr/share/trac/projects/my-project
     
    300286Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory.
    301287
    302 
    303288==== Mapping Static Resources
    304289
     
    321306Assuming the deployment has been done this way:
    322307{{{#!sh
    323 $ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
     308$ trac-admin /var/trac/env deploy /path/to/shared/trac
    324309}}}
    325310
     
    354339}}}
    355340
    356 Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[wiki:TracIni#trac-section| [trac] htdocs_location]] configuration setting:
     341Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
    357342{{{#!ini
    358343[trac]
     
    365350$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
    366351}}}
    367 
    368352
    369353==== Setting up the Plugin Cache
     
    382366 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
    383367
    384 The following document also constains some useful information for beginners: [trac:TracAuthenticationIntroduction].
     368The following document also contains some useful information for beginners: [trac:TracAuthenticationIntroduction].
    385369
    386370== Granting admin rights to the admin user
     
    397381Support for version control systems is provided by optional components in Trac and the components are disabled by default //(since 1.0)//. Subversion and Git must be explicitly enabled if you wish to use them. See TracRepositoryAdmin for more details.
    398382
    399 The components can be enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
     383The version control systems are enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
    400384
    401385{{{#!ini
     
    407391}}}
    408392
    409 After enabling the components, repositories can be configured through the "Repositories" admin panel or by editing [TracIni#repositories-section trac.ini].
    410 
    411 === Automatic reference to the SVN changesets in Trac tickets
    412 
    413 You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas:
    414  * '''`Refs #123`''' - to reference this changeset in `#123` ticket
    415  * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''
    416 
    417 This functionality requires a post-commit hook to be installed as described in [wiki:TracRepositoryAdmin#ExplicitSync TracRepositoryAdmin], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
    418 {{{#!ini
    419 tracopt.ticket.commit_updater.* = enabled
    420 }}}
    421 For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
     393After enabling the components, repositories can be configured through the //Repositories// admin panel or by editing [TracIni#repositories-section trac.ini]. Automatic changeset references can be inserted as ticket comments by configuring [TracRepositoryAdmin#Automaticchangesetreferencesintickets CommitTicketUpdater].
    422394
    423395=== Using Trac
     
    425397Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.
    426398
    427 Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.
     399Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [TracPermissions permissions] to authenticated users to see the full set of features.
    428400
    429401'' Enjoy! ''