Changes between Initial Version and Version 1 of TracInstall

Dec 24, 2012, 8:38:01 PM (10 years ago)



  • TracInstall

    v1 v1  
     1= Trac Installation Guide for 1.0 =
     4Trac is written in the Python programming language and needs a database, [ SQLite], [ PostgreSQL], or [ MySQL]. For HTML rendering, Trac uses the [ Genshi] templating system.
     6Since 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.
     8If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [[trac:TracL10N]].
     10What 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.
     12[[PageOutline(2-3,Installation Steps,inline)]]
     14== Dependencies ==
     15=== Mandatory Dependencies
     16To install Trac, the following software packages must be installed:
     18 * [ Python], version >= 2.5 and < 3.0
     19   (note that we dropped the support for Python 2.4 in this release)
     20 * [ setuptools], version >= 0.6, or better yet, [ distribute]
     21 * [ Genshi], version >= 0.6 (unreleased version 0.7dev should work as well)
     23You also need a database system and the corresponding python bindings.
     24The database can be either SQLite, PostgreSQL or MySQL.
     26==== For the SQLite database #ForSQLite
     28As 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).
     30However, if you'd like, you can download the latest and greatest version of [[trac:Pysqlite]] from
     31[ google code], where you'll find the Windows
     32installers or the `tar.gz` archive for building from source:
     34$ tar xvfz <version>.tar.gz
     35$ cd <version>
     36$ python build_static install
     39This will download the latest SQLite code and build the bindings.
     41SQLite 2.x is no longer supported.
     43A known bug PySqlite versions 2.5.2-4 prohibits upgrade of trac databases
     44from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
     45older. See #9434 for more detail.
     47See additional information in [trac:PySqlite PySqlite].
     49==== For the PostgreSQL database #ForPostgreSQL
     51You need to install the database and its Python bindings:
     52 * [ PostgreSQL], version 8.0 or later
     53 * [ psycopg2]
     55See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
     58==== For the MySQL database #ForMySQL
     60Trac can now work quite well with MySQL, provided you follow the guidelines.
     62 * [ MySQL], version 5.0 or later
     63 * [ MySQLdb], version 1.2.2 or later
     65It is '''very''' important to read carefully the  [trac:MySqlDb] page before creating the database.
     67=== Optional Dependencies
     69==== Version Control System ====
     71===== Subversion =====
     72 * [ 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.
     74There are [ 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 [ Algazam], which works for me under Python 2.6.)
     76Note that Trac '''doesn't''' use [ PySVN], neither does it work yet with the newer `ctype`-style bindings.
     79'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
     82===== Others =====
     84Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].
     86==== Web Server ====
     87A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below.
     89Alternatively you configure Trac to run in any of the following environments.
     90 * [ Apache] with
     91   - [ mod_wsgi], see [wiki:TracModWSGI] and
     93   - [ mod_python 3.3.1], deprecated: see TracModPython)
     94 * a [ FastCGI]-capable web server (see TracFastCgi)
     95 * an [ AJP]-capable web
     96   server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
     97 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script
     98   is highly discouraged''', better use one of the previous options.
     101==== Other Python Packages ====
     103 * [ Babel], version >= 0.9.5,
     104   needed for localization support (unreleased version 1.0dev should work as well)
     105 * [ docutils], version >= 0.3.9
     106   for WikiRestructuredText.
     107 * [ Pygments] for
     108   [wiki:TracSyntaxColoring syntax highlighting].
     109   [ SilverCity] and/or
     110   [ Enscript] may still be used
     111   but are deprecated and you really should be using Pygments.
     112 * [ pytz] to get a complete list of time zones,
     113   otherwise Trac will fall back on a shorter list from
     114   an internal time zone implementation.
     116'''Attention''': The various available versions of these dependencies are not necessarily interchangable, 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].
     118Please 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!).
     121== Installing Trac ==
     122=== Using `easy_install`
     123One way to install Trac is using [ setuptools].
     124With setuptools you can install Trac from the subversion repository;
     126A few examples:
     128 - install Trac 1.0:
     129   {{{
     130   easy_install Trac==1.0
     131   }}}
     132   (NOT YET ENABLED)
     133 - install latest development version 1.0dev:
     134   {{{
     135   easy_install Trac==dev
     136   }}}
     137   Note that in this case you won't have the possibility to run a localized version of Trac;
     138   either use a released version or install from source
     140=== Using `pip`
     141'pip' is an easy_install replacement that is very useful to quickly install python packages.
     142To get a trac installation up and running in less than 5 minutes:
     144Assuming you want to have your entire pip installation in `/opt/user/trac`
     146 -
     148pip -E /opt/user/trac install trac psycopg2
     151 -
     153pip -E /opt/user/trac install trac mysql-python
     156Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings.
     158pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on and create a self contained installation in `/opt/user/trac`.
     160All 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)
     162Additionally, you can install several trac plugins (listed [ here]) through pip.
     166=== From source
     167Of course, using the python-typical setup at the top of the source directory also works.
     169You 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).
     172$ python ./ install
     175''You'll need root permissions or equivalent for this step.''
     177This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
     178of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates.
     180The 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.
     182If 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):
     184$ python ./ install
     186Alternatively, you can do a `bdist_egg` and copy the .egg from dist/ to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
     188=== Advanced Options ===
     190To install Trac to a custom location, or find out about other advanced installation options, run:
     192easy_install --help
     195Also see [ Installing Python Modules] for detailed information.
     197Specifically, you might be interested in:
     199easy_install --prefix=/path/to/installdir
     201or, if installing Trac to a Mac OS X system:
     203easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
     205Note: If installing on Mac OS X 10.6 running {{{ easy_install }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default
     207The 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.
     210== Creating a Project Environment ==
     212A [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.
     214A new environment is created using [wiki:TracAdmin trac-admin]:
     216$ trac-admin /path/to/myproject initenv
     219[TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value.
     221Using the default database connection string in particular will always work as long as you have SQLite installed.
     222For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
     224Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it.
     226Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
     228Finally, 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:
     230# chown -R apache.apache /path/to/myproject
     233{{{#!div class=important
     234'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
     238== Deploying Trac
     240=== Running the Standalone Server ===
     242After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
     244$ tracd --port 8000 /path/to/myproject
     247Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:
     249$ tracd -s --port 8000 /path/to/myproject
     252=== Running Trac on a Web Server ===
     254Trac provides various options for connecting to a "real" web server:
     255 - [wiki:TracFastCgi FastCGI]
     256 - [wiki:TracModWSGI mod_wsgi]
     257 - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)//
     258 - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)//
     260Trac 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], [ uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.
     262==== Generating the Trac cgi-bin directory ==== #cgi-bin
     264In 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].
     266There 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:
     268mkdir -p /usr/share/trac/projects/my-project
     269trac-admin /usr/share/trac/projects/my-project initenv
     270trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
     271mv /tmp/deploy/* /usr/share/trac
     275==== Mapping Static Resources ====
     277Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).
     279Web servers such as [ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.
     281There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.
     283Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the [TracAdmin trac-admin]` <environment> deploy` command:
     286The target `<directory>` will then contain an `htdocs` directory with:
     287 - `site/` - a copy of the environment's directory `htdocs/`
     288 - `common/` - the static resources of Trac itself
     289 - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
     291===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example
     293Assuming the deployment has been done this way:
     295$ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
     298Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
     300Alias /trac/chrome/common /path/to/trac/htdocs/common
     301Alias /trac/chrome/site /path/to/trac/htdocs/site
     303<Directory "/path/to/www/trac/htdocs">
     304  Order allow,deny
     305  Allow from all
     309If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
     311<Location "/trac/chrome/common/">
     312  SetHandler None
     316Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
     318Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
     320Alias /trac/chrome/site /path/to/projectenv/htdocs
     322<Directory "/path/to/projectenv/htdocs">
     323  Order allow,deny
     324  Allow from all
     328Alternatively 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:
     331htdocs_location =
     333Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [ cookie-less]).
     335Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
     337$ ln -s /path/to/trac/htdocs/common /var/www/
     341==== Setting up the Plugin Cache ====
     343Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the PYTHON_EGG_CACHE environment variable. Refer to your server documentation for detailed instructions on how to set environment variables.
     345== Configuring Authentication ==
     347Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the REMOTE_USER variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
     349The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
     351Please refer to one of the following sections:
     352 * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
     353 * [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi` of course, but the same instructions applies also for `mod_python`, `mod_fcgi` or `mod_fastcgi`.
     354 * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
     356== Granting admin rights to the admin user
     357Grant admin rights to user admin:
     359$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
     361This user will have an "Admin" entry menu that will allow you to admin your trac project.
     363== Finishing the install
     365=== Automatic reference to the SVN changesets in Trac tickets ===
     367You 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:
     368 * '''`Refs #123`''' - to reference this changeset in `#123` ticket
     369 * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''
     371This 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.
     373tracopt.ticket.commit_updater.* = enabled
     375For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
     377=== Using Trac ===
     379Once 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.
     381Keep 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.
     383'' Enjoy! ''
     385[trac:TracTeam The Trac Team]
     388See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions