Bienvenue sur

Bienvenue sur , le site de la communauté des utilisateurs francophones de PostGIS.

PostGIS ajoute le support d'objets géographique à la base de données PostgreSQL. En effet, PostGIS "spatialise" le serverur PostgreSQL, ce qui permet de l'utiliser comme une base de données SIG.

Maintenu à jour, en fonction de nos disponibilités et des diverses sorties des outils que nous testons, nous vous proposons l'ensemble de nos travaux publiés en langue française.

Changes between Initial Version and Version 1 of TracInstall

21/09/2011 00:47:47 (11 years ago)



  • TracInstall

    v1 v1  
     2#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc;" 
     4  '''NOTE: this page is for 0.12dev (trunk), the version currently in development. For installing previous Trac versions, please refer to [[0.11/TracInstall]]''' 
     6= Trac Installation Guide for 0.12dev =  
     9Trac is written in the Python programming language and needs a database, [ SQLite], [ PostgreSQL], or [ MySQL]. For HTML rendering, Trac uses the [ Genshi] templating system. 
     11Since 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. 
     13If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at ["TracL10N"]. 
     15What 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 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. 
     17[[PageOutline(2-3,Installation Steps,inline)]] 
     19== Dependencies == 
     20=== Mandatory Dependencies 
     21To install Trac, the following software packages must be installed: 
     23 * [ Python], version >= 2.4 and < 3.0 
     24   (note that we dropped the support for Python 2.3 in this release) 
     25 * [ setuptools], version >= 0.6 
     26 * [ Genshi], version >= 0.6 
     28You also need a database system and the corresponding python bindings. 
     29The database can be either SQLite, PostgreSQL or MySQL. 
     31==== For the SQLite database #ForSQLite 
     33If you're using Python 2.5 or 2.6, you already have everything you need. 
     35If you're using Python 2.4 and need pysqlite, you can download from  
     36[ google code] the Windows 
     37installers or the tar.gz archive for building from source:  
     39$ tar xvfz <version>.tar.gz  
     40$ cd <version>  
     41$ python build_static install  
     44This will extract the SQLite code and build the bindings.  
     46SQLite 2.x is no longer supported. For SQLite 3.x, the pysqlite 1.1.x 
     47bindings are also no longer supported, use pysqlite 2.x. 
     49See additional information in [trac:PySqlite PySqlite]. 
     51==== For the PostgreSQL database #ForPostgreSQL 
     53You need to install the database and its Python bindings: 
     54 * [ PostgreSQL] 
     55 * [ psycopg2] 
     57See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details. 
     60==== For the MySQL database #ForMySQL 
     62Trac can now work quite well with MySQL, provided you follow the guidelines. 
     64 * [ MySQL], version 5.0 or later 
     65 * [ MySQLdb], version 1.2.2 or later 
     67It is '''very''' important to read carefully the  [trac:MySqlDb MySqlDb] page before creating the database. 
     69=== Optional Dependencies 
     71==== Version Control System ==== 
     73===== Subversion ===== 
     74 * [ 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. 
     76There are [ pre-compiled SWIG bindings] available for various platforms. Note 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 PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend]. 
     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], 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 following options,  
     101==== Other Python Packages ==== 
     103 * [ Babel], version >= 0.9.5,  
     104   needed for localization support 
     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 MailingList] or [trac:IrcChannel 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 0.12 beta1:: 
     129   {{{ 
     130   easy_install Trac==0.12b1 
     131   }}} 
     133 - install latest development version 0.12dev 
     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=== From source 
     141Of course, using the python-typical setup at the top of the source directory also works. 
     143You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. Trac-0.12b1.tar.gz), or you can get the source directly from the repository (see Trac:SubversionRepository for details). 
     146$ python ./ install 
     149''You'll need root permissions or equivalent for this step.'' 
     151This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory 
     152of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates. 
     154The 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. 
     156If you install from source and want to make Trac available in other languages, make sure you have installed Babel and then run this additional step before doing the `install` (or simply redo the `install` afterwards): 
     158$ python ./ compile_catalog -f 
     160(the `-f` flag is needed as long as some translations are marked ''fuzzy'', i.e. incomplete, which will most probably be the case during the whole development period, as  strings are continuously added or modified) 
     163=== Advanced Options === 
     165To install Trac to a custom location, or find out about other advanced installation options, run: 
     167easy_install --help 
     170Also see [ Installing Python Modules] for detailed information. 
     172Specifically, you might be interested in: 
     174easy_install --prefix=/path/to/installdir 
     176or, if installing Trac to a Mac OS X system: 
     178easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages 
     180Note: 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 
     182The 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. 
     185== Creating a Project Environment == 
     187A [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. 
     189A new environment is created using [wiki:TracAdmin trac-admin]: 
     191$ trac-admin /path/to/myproject initenv 
     194[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.  
     196Using the default database connection string in particular will always work as long as you have SQLite installed. 
     197For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point. 
     199Since 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. 
     201Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file. 
     203Finally, 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: 
     205# chown -R apache.apache /path/to/myproject 
     208== Running the Standalone Server == 
     210After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]: 
     212$ tracd --port 8000 /path/to/myproject 
     215Then, 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: 
     217$ tracd -s --port 8000 /path/to/myproject 
     220== Running Trac on a Web Server == 
     222Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi. 
     224Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. 
     226==== Generating the Trac cgi-bin directory ==== 
     228In 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]. 
     230There 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: 
     232mkdir -p /usr/share/trac/projects/my-project 
     233trac-admin /usr/share/trac/projects/my-project initenv 
     234trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy 
     235mv /tmp/deploy/* /usr/share/trac 
     238==== Setting up the Plugin Cache ==== 
     240Some 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. 
     242== Configuring Authentication == 
     244The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. The basic procedure is described in the [wiki:TracCgi#AddingAuthentication "Adding Authentication"] section on the TracCgi page. To learn how to setup authentication for the frontend you're using, please refer to one of the following pages: 
     246 * TracStandalone if you use the standalone server, `tracd`. 
     247 * TracCgi if you use the CGI or FastCGI web front ends. 
     248 * [wiki:TracModWSGI] if you use the Apache mod_wsgi web front end. 
     249 * TracModPython if you use the Apache mod_python web front end. 
     252== Automatic reference to the SVN changesets in Trac tickets == 
     254You 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: 
     255 * '''`Refs #123`''' - to reference this changeset in `#123` ticket 
     256 * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed'' 
     258This 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. 
     260tracopt.ticket.commit_updater.* = enabled 
     262For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel. 
     264== Using Trac == 
     266Once 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. 
     268Keep in mind that anonymous (not logged in) users can by default access most but not all of the features. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features. 
     270'' Enjoy! '' 
     272[trac:TracTeam The Trac Team] 
     275See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions