Changes between Version 1 and Version 2 of TracAdmin

Jun 5, 2014, 8:41:08 PM (10 years ago)



  • TracAdmin

    v1 v2  
     4Trac 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.
     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).
     8== Usage ==
     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:
    5 #!html
    6 Trac may be administered via the <a href="../admin">admin</a> page.
     12trac-admin /path/to/projenv wiki list
     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.
     18If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:
     20trac-admin /path/to/projenv help
     23Some commands have a more detailed help, which you can access by specifying the command's name as a subcommand for `help`:
     26trac-admin /path/to/projenv help <command>
     29=== `trac-admin <targetdir> initenv` === #initenv
     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.
     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.
     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.
     40== Interactive Mode ==
     42When passing the environment path as the only argument, `trac-admin` starts in interactive mode.
     43Commands can then be executed on the selected environment using the prompt, which offers tab-completion
     44(on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.
     46Once you're in interactive mode, you can also get help on specific commands or subsets of commands:
     48For example, to get an explanation of the `resync` command, run:
     50> help resync
     53To get help on all the Wiki-related commands, run:
     55> help wiki
     58== Full Command Reference ==
     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.