Äîêóìåíò âçÿò èç êýøà ïîèñêîâîé ìàøèíû. Àäðåñ îðèãèíàëüíîãî äîêóìåíòà : http://kodomo.cmm.msu.su/trac/tanchiki/wiki/TracAdmin?action=diff&version=2
Äàòà èçìåíåíèÿ: Unknown
Äàòà èíäåêñèðîâàíèÿ: Mon Apr 11 03:28:20 2016
Êîäèðîâêà: IBM-866
TracAdmin (diff) òÀÓ Tanchiki

Changes between Version 1 and Version 2 of TracAdmin


Ignore:
Timestamp:
08/21/13 19:46:14 (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracAdmin

    v1 v2 ˆà
    44Trac is distributed with a powerful command-line configuration tool. This tool can be used  to configure and customize your Trac-installation to better fit your needs.ˆà
    55ˆà
    6ˆàSome of those operations can also be performed via the ''Admin'' web interface, an updated version of the [http://trac.edgewall.org/wiki/WebAdmin WebAdmin] plugin now integrated within Trac (since version 0.11).ˆà
    ˆà6Some of those operations can also be performed via the ''Admin'' web interface, an updated version of the [trac:WebAdmin] plugin now integrated within Trac (since version 0.11).ˆà
    77ˆà
    88== Usage ==ˆà
    99ˆà
    10ˆàYou can get a comprehensive list of the available options, commands and sub-commands by invoking `trac-admin` with the `help` command:.ˆà
    11ˆà{{{ˆà
    12ˆàtrac-admin helpˆà
    13ˆà}}}ˆà
    14ˆàˆà
    15ˆàUnless you're executing the `help`, `about` or `version` sub-commands, you'll need to specify the path to the TracEnvironment that you want to administer as the first argument, for example:ˆà
    ˆà10For nearly every `trac-admin` command, you'll need to specify the path to the TracEnvironment that you want to administer as the first argument, for example:ˆà
    1611{{{ˆà
    1712trac-admin /path/to/projenv wiki listˆà
    1813}}}ˆà
    ˆà14ˆà
    ˆà15The only exception is for the `help` command, but even in this case if you omit the environment, you'll only get a very succinct list of commands (`help` and `initenv`), the same list you'd get when invoking `trac-admin` alone.ˆà
    ˆà16Also, `trac-admin --version` will tell you about the Trac version (e.g. 0.12) corresponding to the program.ˆà
    ˆà17ˆà
    ˆà18If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:ˆà
    ˆà19{{{ˆà
    ˆà20trac-admin /path/to/projenv helpˆà
    ˆà21}}}ˆà
    ˆà22ˆà
    ˆà23Some commands have a more detailed help, which you can access by specifying the command's name as a subcommand for `help`:ˆà
    ˆà24ˆà
    ˆà25{{{ˆà
    ˆà26trac-admin /path/to/projenv help <command>ˆà
    ˆà27}}}ˆà
    ˆà28ˆà
    ˆà29=== `trac-admin <targetdir> initenv` === #initenvˆà
    ˆà30ˆà
    ˆà31This subcommand is very important as it's the one used to create a TracEnvironment in the specified `<targetdir>`. That directory must not exist prior to the call.ˆà
    ˆà32ˆà
    ˆà33[[TracAdminHelp(initenv)]]ˆà
    ˆà34ˆà
    ˆà35It supports an extra `--inherit` option, which can be used to specify a global configuration file which can be used share settings between several environments. You can also inherit from a shared configuration afterwards, by setting the `[inherit] file` option in the `conf/trac.ini` file in your newly created environment, but the advantage of specifying the inherited configuration file at environment creation time is that only the options ''not'' already specified in the global configuration file will be written in the created environment's `conf/trac.ini` file.ˆà
    ˆà36See TracIni#GlobalConfiguration.ˆà
    ˆà37ˆà
    ˆà38Note that in version 0.11 of Trac, `initenv` lost an extra last argument `<templatepath>`, which was used in previous versions to point to the `templates` folder. If you are using the one-liner '`trac-admin /path/to/trac/ initenv <projectname> <db> <repostype> <repospath>`' in the above and getting an error that reads ''''`Wrong number of arguments to initenv: 4`'''', then this is because you're using a `trac-admin` script from an '''older''' version of Trac.ˆà
    1939ˆà
    2040== Interactive Mode ==ˆà
    òÀæ òÀæ ˆà
    3858== Full Command Reference ==ˆà
    3959ˆà
    ˆà60You'll find below the detailed help for all the commands available by default in `trac-admin`. Note that this may not match the list given by `trac-admin <yourenv> help`, as the commands  pertaining to components disabled in that environment won't be available and conversely some plugins activated in the environment can add their own commands.ˆà
    ˆà61ˆà
    4062[[TracAdminHelp()]]ˆà
    41ˆàˆà
    42ˆàˆà
    43ˆà=== Notes ===ˆà
    44ˆàˆà
    45ˆàThe `initenv` also supports an extra `--inherit` option, which can be used to specify the `[inherit] file` option at environment creation time so that only the options ''not'' already specified in the global configuration file will be written in the conf/trac.ini file of the newly created environment.ˆà
    46ˆàSee TracIni#GlobalConfiguration.ˆà
    47ˆàˆà
    48ˆàNote that in version 0.11 of Trac, `initenv` lost an extra last argument `<templatepath>`, which was used in previous versions to point to the `templates` folder. If you are using the one-liner '`trac-admin /path/to/trac/ initenv <projectname> <db> <repostype> <repospath>`' in the above and getting an error that reads ''''`Wrong number of arguments to initenv: 4`'''', then this is because you're using a `trac-admin` script from an '''older''' version of Trac.ˆà
    4963ˆà
    5064----ˆà