Changes between Version 3 and Version 4 of TracEnvironment


Ignore:
Timestamp:
09/17/06 21:44:10 (18 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracEnvironment

    v3 v4  
    1 = Trac Storage - The Environment =
     1= The Trac Environment =
    22
    3 Trac uses a directory structure and a database for storing project data.
     3Trac uses a directory structure and a database for storing project data. The directory is referred to as the “environment”.
    44
    55== Creating an Environment ==
    … …  
    1111
    1212[wiki:TracAdmin trac-admin] will ask you for the name of the project, the
    13 database connection string (explained below), and where your subversion
    14 repository is located.
     13database connection string (explained below), and the type and path to
     14your source code repository.
    1515
    16   ''Note: The web server user will require file system write permission to
     16''Note: The web server user will require file system write permission to
    1717the environment directory and all the files inside. Please remember to set
    18 the appropriate permissions. The same applies to the Subversion
    19 repository, although Trac will only require read access as long as you're
    20 not using the BDB file system.''
     18the appropriate permissions. The same applies to the Subversion repository
     19Trac is eventually using, although Trac will only require read access as long
     20as you're not using the BDB file system.''
    2121
    2222== Database Connection Strings ==
    2323
    24 Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and
    25 [http://www.postgresql.org/ PostgreSQL] as database backends.  The default
    26 is to use SQLite, which is probably sufficient for most projects. The database file
    27 is then stored in the environment directory, and can easily be
    28 [wiki:TracBackup backed up] together with the rest of the environment.
     24Since version 0.9, Trac supports both [http://sqlite.org/ SQLite],
     25[http://www.postgresql.org/ PostgreSQL] and [http://mysql.com/ MySQL] as
     26database backends.  The default is to use SQLite, which is probably sufficient
     27for most projects. The database file is then stored in the environment
     28directory, and can easily be [wiki:TracBackup backed up] together with the
     29rest of the environment.
    2930
    3031The connection string for an embedded SQLite database is:
    … …  
    3334}}}
    3435
    35 If you want to use PostgreSQL instead, you'll have to use a different
    36 connection string. For example, to connect to a database on the same
    37 machine called `trac`, that allows access to the user `johndoe` with
    38 the password `letmein`, use:
     36If you want to use PostgreSQL or MySQL instead, you'll have to use a
     37different connection string. For example, to connect to a PostgreSQL
     38database on the same machine called `trac`, that allows access to the
     39user `johndoe` with the password `letmein`, use:
    3940{{{
    4041postgres://johndoe:letmein@localhost/trac
    … …  
    4849Note that with PostgreSQL you will have to create the database before running
    4950`trac-admin initenv`.
     51
     52And make sure PostgreSQl DB name is "trac". What worked for me:
     53And didn't work uppercase trac-user-name
     54{{{
     55sudo su - postgres -c createdb trac
     56sudo su - postgres -c psql trac
     57CREATE USER trac-user-name WITH PASSWORD 'trac-pass-name';
     58}}}
     59
     60== Source Code Repository ==
     61
     62You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion,
     63which is the default), then the ''path'' where the repository is located.
     64
     65If you don't want to use Trac with a source code repository, simply leave the ''path'' empty
     66(the ''type'' information doesn't matter, then).
     67
     68For some systems, it is possible to specify not only the path to the repository,
     69but also a ''scope'' within the repository. Trac will then only show information
     70related to the files and changesets below that scope. The Subversion backend for
     71Trac supports this; for other types, check the corresponding plugin's documentation.
     72
     73Example of a configuration for a Subversion repository:
     74{{{
     75[trac]
     76repository_type = svn
     77repository_dir = /path/to/your/repository
     78}}}
     79
     80The configuration for a scoped Subversion repository would be:
     81{{{
     82[trac]
     83repository_type = svn
     84repository_dir = /path/to/your/repository/scope/within/repos
     85}}}
    5086
    5187== Directory Structure ==
    … …  
    67103 * `wiki-macros` - Environment-specific [wiki:WikiMacros Wiki macros].
    68104
     105  '''Note: don't confuse a Trac environment directory with the source code repository directory.
     106It happens that the above structure is loosely modelled after the Subversion repository directory
     107structure, but they are not and ''must not'' be located at the same place.'''
     108
    69109----
    70110See also: TracAdmin, TracBackup, TracIni, TracGuide