Legend:

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.

6

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.

5

7

6

Some 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

Some of those configurations can also be performed via the web administration module.

7

9

8

== Usage ==

10

== Usage

9

11

10

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

For nearly every `trac-admin` command, you will need to specify the path to the TracEnvironment that you want to administer as the first argument:

11

13

{{{

12

14

trac-admin /path/to/projenv wiki list

13

15

}}}

14

16

15

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

The 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.

16

18

Also, `trac-admin --version` will tell you about the Trac version (e.g. 0.12) corresponding to the program.

17

19

18

If you want to get a comprehensive list of the available commands and sub-commands, you need to specify an existing environment:

20

To get a comprehensive list of the available commands and sub-commands, specify an existing environment:

This subcommand is very important as it's the one used to create a TracEnvironment in the specified `<targetdir>`. That directory must not exists prior to the call.

32

This 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.

32

33

33

34

[[TracAdminHelp(initenv)]]

34

35

35

It 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.

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.

36

37

See TracIni#GlobalConfiguration.

37

38

38

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.

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 get an error that reads `Wrong number of arguments to initenv: 4`, then this is because you are using a `trac-admin` script from an '''older''' version of Trac.

39

40

40

== Interactive Mode ==

41

== Interactive Mode

41

42

42

43

When passing the environment path as the only argument, `trac-admin` starts in interactive mode.

(on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.

45

46

46

Once you're in interactive mode, you can also get help on specific commands or subsets of commands:

47

Once you are in interactive mode, you can also get help on specific commands or subsets of commands:

47

48

48

49

For example, to get an explanation of the `resync` command, run:

49

50

{{{

50

> help resync

51

$ help resync

51

52

}}}

52

53

53

54

To get help on all the Wiki-related commands, run:

54

55

{{{

55

> help wiki

56

$ help wiki

56

57

}}}

57

58

58

== Full Command Reference ==

59

== Full Command Reference

59

60

60

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.

61

You 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 can add their own commands.