Changes between Version 20 and Version 21 of TracTroubleshooting

Timestamp:

May 15, 2017, 7:58:42 AM (7 years ago)

Author:

Ryan J Ollos

Comment:

Remove obsolete info about running trac standalone.

TracTroubleshooting

@@ -69 +69 @@
 TracStandalone is the indispensable companion whether you intend to develop or debug Trac. In particular, check out the `-r` (auto-reload) feature, which will make Trac notice any change to one of its source file and restart automatically. You can therefore see Trac react immediately to your code changes, provided you don't have syntax errors outside of a method.
 
-In this setup, you're free to try out modification, dump additional information to the log or insert direct `print` statements; an ugly but effective way of debugging.
+In this setup, you're free to try out modifications, dump additional information to the log or insert direct `print` statements; an ugly but effective way of debugging.
 
-It may even be possible to run `tracd` with a debugger, but not explored here.
+It may even be possible to run `tracd` with a debugger, but that is not explored here.
 
 Best is to start from a [TracSubversion checkout] of the pristine source code you're interested to debug or develop for. 
 Then, you can run the standalone server by doing:
 {{{#!sh
-$ python scripts/tracd <options>
+$ tracd <options>
 }}}
 
-If you're using [source:trunk] (Trac [milestone:0.11]dev), since the SetupTools integrations, you'll have to run the standalone module directly: 
+Note that the very first time in a fresh working copy, you'll have to install the code in develop mode:
 {{{#!sh
-$ python trac/web/standalone.py <options>
-}}}
-
-Note that the very first time in a fresh working copy, you'll have to at least initialize the ''Trac.egg-info'' folder, by doing:
-{{{#!sh
-$ python setup.py egg_info
+$ python setup.py develop
 }}}