Changes between Version 13 and Version 14 of TracTroubleshooting

Timestamp:

Jun 4, 2015, 6:37:40 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Add syntax highlighting.

TracTroubleshooting

@@ -54 +54 @@
 As this template engine is also written in Python, no specific data format is needed and a simple Python dictionary is used to feed the engine. It's very easy to inspect any part of this data by modifying the template and inserting `${pprint(...)}` statements, possibly in between `<pre>...</pre>` tags.
 Each modification to a template will be detected on the fly and you'll be able to see the result of the change immediately, provided you have the following setup in your TracIni:
-{{{
+{{{#!ini
 [trac]
 auto_reload = yes
@@ -69 +69 @@
 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>
 }}}
 
 If you're using [source:trunk] (Trac [milestone:0.11]dev), since the SetupTools integrations, you'll have to run the standalone module directly: 
-{{{
+{{{#!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
 }}}
@@ -96 +96 @@
 
 Getting a backtrace for `tracd`:
-{{{
+{{{#!sh
 $ gdb $(which python)
 (gdb) run /opt/trac-0.10/scripts/tracd -p 8080 /srv/trac/yourproject
@@ -103 +103 @@
 
 Getting a backtrace for Apache's `httpd` can be done in a similar way:
-{{{
+{{{#!sh
 $ apachectl -k stop
 $ gdb $(which httpd)
@@ -115 +115 @@
 
 Here it might be interesting to just "attach" to an already running process:
-{{{
+{{{#!sh
 $ ps -ef | grep httpd 
 ...