Changes between Version 5 and Version 6 of TracAdmin


Ignore:
Timestamp:
04/19/23 14:06:21 (20 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracAdmin

    v5 v6  
    1 = TracAdmin =
    2 [[PageOutline(2-5, Contents, floated)]]
     1= TracAdmin
     2
     3[[PageOutline(2-5, Contents, pullout)]]
    34[[TracGuideToc]]
    45
    5 Trac 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.
     6Trac 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.
    67
    7 Some of those operations can also be performed via the WebAdmin interface.
     8Some of the configurations can also be performed via the web administration module.
    89
    9 == Usage ==
     10== Usage
    1011
    11 For 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:
    12 {{{
    13 trac-admin /path/to/projenv wiki list
     12For nearly every `trac-admin` command, the first argument must be the path to the TracEnvironment:
     13{{{#!sh
     14$ trac-admin /path/to/projenv wiki list
    1415}}}
    1516
    16 The 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.
    17 Also, `trac-admin --version` will tell you about the Trac version (e.g. 0.12) corresponding to the program.
     17The only exception is for the `help` command, but even in this case, if you omit the environment you will only get a very succinct list of commands (`help` and `initenv`), the same list you would get when invoking `trac-admin` alone.
     18`trac-admin --version` will tell you about the Trac version (e.g. 1.2) corresponding to the program.
    1819
    19 If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:
    20 {{{
    21 trac-admin /path/to/projenv help
     20To get a comprehensive list of the available commands and sub-commands, specify the path to an environment followed by the subcommand `help`:
     21{{{#!sh
     22$ trac-admin /path/to/projenv help
    2223}}}
    2324
    24 Some commands have a more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
    25 
    26 {{{
    27 trac-admin /path/to/projenv help <command>
     25Some commands have more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
     26{{{#!sh
     27$ trac-admin /path/to/projenv help <command>
    2828}}}
    2929
    30 === `trac-admin <targetdir> initenv` === #initenv
     30When an error occurs in a `trac-admin` command the return value will be `2` and any error messages are printed to `stderr`.
    3131
    32 This 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=== `trac-admin <targetdir> initenv` #initenv
     33
     34This subcommand is very important as is the one used to create a TracEnvironment in the specified `<targetdir>`. That directory must not exist prior to the call.
    3335
    3436[[TracAdminHelp(initenv)]]
    3537
    36 It supports an extra `--inherit` option, which can be used to specify a global configuration file which can be used to 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.
     38It supports the `--inherit` option, which specifies a global configuration file for sharing 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. The advantage of specifying the inherited configuration file at environment creation time is that only the options ''not'' specified in the global configuration file will be written to the environment's `conf/trac.ini` file.
    3739See TracIni#GlobalConfiguration.
    3840
    39 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.
     41== Interactive Mode
    4042
    41 == Interactive Mode ==
     43`trac-admin` starts in interactive mode when the environment path is the only argument.
     44Commands can then be executed on the selected environment using the prompt, which offers tab-completion when the Python `readline` module is available. It also offers automatic repetition of the last command issued.
    4245
    43 When passing the environment path as the only argument, `trac-admin` starts in interactive mode.
    44 Commands can then be executed on the selected environment using the prompt, which offers tab-completion
    45 (on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.
     46The `readline` module should be available on all Unix-compatible platforms. For Windows, support can be obtained by installing [https://pypi.python.org/pypi/pyreadline pyreadline].
    4647
    47 Once you're in interactive mode, you can also get help on specific commands or subsets of commands:
    48 
    49 For example, to get an explanation of the `resync` command, run:
    50 {{{
    51 > help resync
     48In interactive mode, you can also get help on specific commands or subsets of commands. For example, to get an explanation of the `resync` command, run:
     49{{{#!sh
     50$ help resync
    5251}}}
    5352
    5453To get help on all the Wiki-related commands, run:
    55 {{{
    56 > help wiki
     54{{{#!sh
     55$ help wiki
    5756}}}
    5857
    59 == Full Command Reference ==
     58== Full Command Reference
    6059
    61 You'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.
     60The commands available by default in `trac-admin` are listed below. 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 may add their own commands.
    6261
    6362[[TracAdminHelp()]]
    6463
    6564----
    66 See also: TracGuide, TracBackup, TracPermissions, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]
     65See also: TracBackup, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]