Changes between Version 1 and Version 2 of TracAdmin
- Timestamp:
- Apr 16, 2016, 7:10:42 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracAdmin
v1 v2 1 = TracAdmin = 1 = TracAdmin 2 3 [[PageOutline(2-5, Contents, floated)]] 2 4 [[TracGuideToc]] 3 5 4 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 operations can also be performed via the web administration module. 7 9 8 == Usage ==10 == Usage 9 11 10 12 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: … … 33 35 [[TracAdminHelp(initenv)]] 34 36 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.37 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 38 See TracIni#GlobalConfiguration. 37 39 38 40 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 41 40 == Interactive Mode ==42 == Interactive Mode 41 43 42 44 When passing the environment path as the only argument, `trac-admin` starts in interactive mode. … … 56 58 }}} 57 59 58 == Full Command Reference ==60 == Full Command Reference 59 61 60 62 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.
