Changes between Initial Version and Version 1 of TracAdmin

Feb 16, 2019, 10:35:19 PM (4 years ago)



  • TracAdmin

    v1 v1  
     1= TracAdmin
     3[[PageOutline(2-5, Contents, pullout)]]
     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.
     8Some of the configurations can also be performed via the web administration module.
     10== Usage
     12For nearly every `trac-admin` command, the first argument must be the path to the TracEnvironment:
     14$ trac-admin /path/to/projenv wiki list
     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.
     20To get a comprehensive list of the available command and sub-command, specify the path to an environment:
     22$ trac-admin /path/to/projenv help
     25Some commands have more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
     27$ trac-admin /path/to/projenv help <command>
     30When an error occurs in a `trac-admin` command the return value will be `2` and error messages are printed to `stderr`.
     32=== `trac-admin <targetdir> initenv` #initenv
     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.
     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.
     39See TracIni#GlobalConfiguration.
     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
     45when the Python `readline` module is available. It also offers automatic repetition of the last command issued.
     47The `readline` module should be available on all Unix-compatible platforms. For Windows, support can be obtained by installing [ pyreadline].
     49Once you are in interactive mode, you can also get help on specific commands or subsets of commands:
     51For example, to get an explanation of the `resync` command, run:
     53$ help resync
     56To get help on all the Wiki-related commands, run:
     58$ help wiki
     61== Full Command Reference
     63You will 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 may add their own commands.
     68See also: TracBackup, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]