16 | | ''Note: Environment のディレクトリ配下は、 Web サーバの実行ユーザに書き込みパーミッションを |
17 | | 与える必要があります。適切なパーミッションの付与を忘れないようにしてください。 |
18 | | 書き込みパーミッションの付与は、 Trac が最終的に使用している Subversion のリポジトリにも当てはまります。 |
19 | | ただし、あなたが Subversion リポジトリに Barkley DB のファイルシステムを使用していないならば、 |
20 | | Trac は読み取りパーミッションしか必要としません。'' |
| 16 | ''Note: The web server user will require file system write permission to |
| 17 | the environment directory and all the files inside. Please remember to set |
| 18 | the appropriate permissions. The same applies to the Subversion repository |
| 19 | Trac is eventually using, although Trac will only require read access as long |
| 20 | as you're not using the BDB file system. Also, it seems that project names |
| 21 | with spaces can be problematic for authentication (see [trac:#7163]).'' |
24 | | バージョン 0.9 以降の Trac では [http://sqlite.org/ SQLite], |
25 | | [http://www.postgresql.org/ PostgreSQL] と [http://mysql.com/ MySQL] をバックエンドのデータベースとして |
26 | | 利用可能になりました。通常では SQLite を使用します。たぶんほとんどのプロジェクトにとっては SQLite で十分です。 |
27 | | データベースファイルは Environment のディレクトリに保存されます。そして、 |
28 | | [wiki:TracBackup Trac のバックアップ] で Environment の残りの部分 (データベースファイル以外のファイル) |
29 | | と一緒にバックアップすることができます。 |
| 25 | Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and |
| 26 | [http://www.postgresql.org/ PostgreSQL] database backends. Preliminary |
| 27 | support for [http://mysql.com/ MySQL] was added in 0.10. The default is |
| 28 | to use SQLite, which is probably sufficient for most projects. The database |
| 29 | file is then stored in the environment directory, and can easily be |
| 30 | [wiki:TracBackup backed up] together with the rest of the environment. |
36 | | もしあなたが、 PostgreSQL や MySQL を代わりに使用する場合、 |
37 | | 異なる接続用文字列を使用しなければなりません。 例えば、 PostgreSQL に接続するとき、 |
38 | | ユーザ名 `johndoe` でパスワード `letmein` で |
39 | | ローカルホストの `trac` と呼ばれるデータベースに接続するには以下のように指定します: |
| 38 | === PostgreSQL Connection String === |
| 39 | If you want to use PostgreSQL or MySQL instead, you'll have to use a |
| 40 | different connection string. For example, to connect to a PostgreSQL |
| 41 | database on the same machine called `trac`, that allows access to the |
| 42 | user `johndoe` with the password `letmein`, use: |
62 | | == ソースコードリポジトリ == |
| 66 | See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL]. |
| 67 | Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`. |
| 68 | {{{ |
| 69 | createuser -U postgres -E -P tracuser |
| 70 | createdb -U postgres -O tracuser -E UTF8 trac |
| 71 | }}} |
| 72 | When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command. Also note that the database should be created as UTF8. LATIN1 encoding causes errors trac's use of unicode in trac. SQL_ASCII also seems to work. |
75 | | Subversion リポジトリの設定の一例です: |
| 87 | If you want to use MySQL instead, you'll have to use a |
| 88 | different connection string. For example, to connect to a MySQL |
| 89 | database on the same machine called `trac`, that allows access to the |
| 90 | user `johndoe` with the password `letmein`, the mysql connection string is: |
| 91 | {{{ |
| 92 | mysql://johndoe:letmein@localhost:3306/trac |
| 93 | }}} |
| 94 | |
| 95 | == Source Code Repository == |
| 96 | |
| 97 | You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion, |
| 98 | which is the default), then the ''path'' where the repository is located. |
| 99 | |
| 100 | If you don't want to use Trac with a source code repository, simply leave the ''path'' empty |
| 101 | (the ''type'' information doesn't matter, then). |
| 102 | |
| 103 | For some systems, it is possible to specify not only the path to the repository, |
| 104 | but also a ''scope'' within the repository. Trac will then only show information |
| 105 | related to the files and changesets below that scope. The Subversion backend for |
| 106 | Trac supports this; for other types, check the corresponding plugin's documentation. |
| 107 | |
| 108 | Example of a configuration for a Subversion repository: |
99 | | * `trac.db` - SQLite データベース (SQLite を使用しているならば) |
100 | | * `plugins` - Environment に固有の [wiki:TracPlugins プラグイン] (Python eggs) |
101 | | * `templates` - カスタム (プロジェクトに固有の) テンプレート |
102 | | * `site_css.cs` - カスタム CSS スタイルシート |
103 | | * `site_footer.cs` - カスタムフッタ |
104 | | * `site_header.cs` - カスタムヘッダ |
105 | | * `wiki-macros` - Environment に固有の [wiki:WikiMacros Wiki マクロ] |
| 132 | * `trac.db` - The SQLite database (if you're using SQLite). |
| 133 | * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(0.11 only)''''' |
| 134 | * `log` - default directory for log files, if logging is turned on and a relative path is given. |
| 135 | * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [milestone:0.10]) |
| 136 | * `templates` - Custom ClearSilver environment-specific templates. '''''(0.10 only)''''' |
| 137 | * `site_css.cs` - Custom CSS rules. |
| 138 | * `site_footer.cs` - Custom page footer. |
| 139 | * `site_header.cs` - Custom page header. |
| 140 | * `templates` - Custom Genshi environment-specific templates. '''''(0.11 only)''''' |
| 141 | * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance |
| 142 | * `wiki-macros` - Environment-specific [WikiMacros Wiki macros]. '''''(0.10 only)''''' |