Mercurial > p > roundup > code

comparison doc/FAQ.txt @ 1585:1cfffe2f54c2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
edited FAQ
author Richard Jones <richard@users.sourceforge.net>
date Thu, 10 Apr 2003 11:00:44 +0000
parents 2090f2004ee3
children ed2c4f5a27da
comparison
equal deleted inserted replaced
1584:2090f2004ee3 1585:1cfffe2f54c2
1 =========== 1 ===========
2 Roundup FAQ 2 Roundup FAQ
3 =========== 3 ===========
4 4
5 :Version: $Revision: 1.12 $ 5 :Version: $Revision: 1.13 $
6
7 NOTE: This is just a grabbag, most of this should go into documentation.
8 6
9 .. contents:: 7 .. contents::
10 8
11 9
12 Installation 10 Installation
13 ------------ 11 ------------
14 12
15 Living without a mailserver. 13 Living without a mailserver
16 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 14 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
17 15
18 Remove the nosy reactor, means delete the tracker file 16 Remove the nosy reactor, means delete the tracker file
19 'detectors/nosyreactor.py'. 17 ``detectors/nosyreactor.py`` from your tracker home.
20 18
21 19
22 Rights issues (MISSING) 20 The cgi-bin is very slow!
23 ~~~~~~~~~~~~~~~~~~~~~~~ 21 ~~~~~~~~~~~~~~~~~~~~~~~~~
24 22
25 Different jobs run under different users. 23 Yep, it sure is. It has to start up Python and load all of the support
24 libraries for *every* request.
26 25
27 * Standalone roundup-server is started by whome ? 26 The solution is to use the built in server.
28 27
29 * Running cgi under apache. 28 To make Roundup more seamless with your website, you may place the built
30 29 in server behind apache and link it into your web tree
31 * roundup-mailgw called via .forward from MTA, or running a cron job
32 fetching via pop.
33 30
34 31
32 How do I put Roundup behind Apache
33 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
35 34
36 The cgibin is very slow! 35 We have a project (foo) running on ``foohost.com:8888``.
37 ~~~~~~~~~~~~~~~~~~~~~~~~ 36 We want ``http://foohost.com/FooIssues`` to use the roundup server, so we
38 Yep, it sure is. It has to do database open/operation/close 37 set that up on port 8888 on ``foohost.com`` with the ``config.py`` line::
39 _every_ request.
40
41 Solution:
42 * use the built in server
43 * place the built in server behind apache and link it into your web tree
44
45
46
47 How do I put it behind apache
48 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
49 We have a project (foo) running on foohost.com:8888.
50 We want http://foohost.com/FooIssues to use the roundup server, so we
51 set that up on port 8888 on foohost.com with the config.py line:
52 38
53 TRACKER_WEB = 'http://foohost.com/FooIssues/' 39 TRACKER_WEB = 'http://foohost.com/FooIssues/'
54 40
55 We have a foo_issues project/tracker configured on roundup and we run the 41 We have a "foo_issues" tracker and we run the server with::
56 server with:
57 ~/bin/roundup-server -p 8888 foo_issues=/home/roundup/trackers/foo_issues
58 42
43 roundup-server -p 8888 foo_issues=/home/roundup/trackers/foo_issues
59 44
60 Then, on the 'front end' host (redhat 7.3 with apache 1.3), in 45 Then, on the Apache machine (eg. redhat 7.3 with apache 1.3), in
61 /etc/httpd/conf/httpd.conf uncomment: 46 ``/etc/httpd/conf/httpd.conf`` uncomment::
62 47
63 LoadModule proxy_module modules/libproxy.so 48 LoadModule proxy_module modules/libproxy.so
64 and 49
50 and::
51
65 AddModule mod_proxy.c 52 AddModule mod_proxy.c
66 53
67 Then add: 54 Then add::
68 55
69 # roundup stuff (added manually) 56 # roundup stuff (added manually)
70 <IfModule mod_proxy.c> 57 <IfModule mod_proxy.c>
71 58
72 RewriteEngine on 59 RewriteEngine on
82 RewriteRule ^/FooIssues$ FooIssues/ [R] 69 RewriteRule ^/FooIssues$ FooIssues/ [R]
83 RewriteRule ^/FooIssues/(.*) http://foohost.com:8888/foo_issues/$1 [P] 70 RewriteRule ^/FooIssues/(.*) http://foohost.com:8888/foo_issues/$1 [P]
84 71
85 </IfModule> 72 </IfModule>
86 73
87 Then restart apache. 74 Then restart Apache. Now Apache will proxy the request on to the
75 roundup-server.
88 76
89 Now apache will proxy the request on to the roundup server. 77 You need to add the last 3 RewriteRule lines for each tracker that you have.
90
91 Obviously you need to add the last 3 RewriteRule lines for each
92 project/tracker that you have.
93 78
94 You can now firewall off port 8888 from the rest of the world. 79 You can now firewall off port 8888 from the rest of the world.
95
96
97
98
99 80
100 81
101 Templates 82 Templates
102 --------- 83 ---------
103 84
104 What is that stuff in ~/trackers/foo_issues/html/* 85 What is that stuff in the tracker html directory?
105 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 86 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
106 This is the template code that roundup uses to display the various pages.
107 87
108 This is bases upon the template markup language in zope. 88 This is the template code that Roundup uses to display the various pages.
109 89 This is based upon the template markup language in Zope called, oddly
110 Have a look at: 90 enough "Zope Page Templates". There's documentation in the Roundup
91 customisation_ documentation. For more information have a look at:
111 92
112 http://www.zope.org/Documentation/Books/ZopeBook/current/contents 93 http://www.zope.org/Documentation/Books/ZopeBook/current/contents
113 94
114 chapter 5 Using Zope Page Templates 95 specifically chapter 5 "Using Zope Page Templates" and chapter 9 "Advanced
115 and chapter 9 Advanced Page Templates 96 Page Templates".
116 97
117 98
118 But I just want a select/option list for .... 99 But I just want a select/option list for ....
119 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 100 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
120 Really easy...
121 101
122 Edit issue.item 102 Really easy... edit ``html/issue.item``. For 'nosy', change line 53 from::
123 103
124 For 'nosy', change line 53 from:
125 <span tal:replace="structure context/nosy/field" /> 104 <span tal:replace="structure context/nosy/field" />
126 to 105
106 to::
107
127 <span tal:replace="structure context/nosy/menu" /> 108 <span tal:replace="structure context/nosy/menu" />
128 109
129 For 'assigned to', change line 61 from: 110 For 'assigned to', change line 61 from::
111
130 <td tal:content="structure context/assignedto/field">assignedto menu</td> 112 <td tal:content="structure context/assignedto/field">assignedto menu</td>
131 to: 113
114 to::
115
132 <td tal:content="structure context/assignedto/menu">assignedto menu</td> 116 <td tal:content="structure context/assignedto/menu">assignedto menu</td>
133
134 get the idea?
135 117
136 118
137 119
138 Great! But now the select/option list is too big 120 Great! But now the select/option list is too big
139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 121 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
122
140 Thats a little harder (but only a little ;^) 123 Thats a little harder (but only a little ;^)
141 124
142 Edit issue.item 125 Again, edit ``html/issue.item``. For nosy, change line 53 from:
143 126
144 For nosy, change line 53 from: 127 <span tal:replace="structure context/nosy/field" />
145 (see above) 128
146 to 129 to::
130
147 <span tal:replace="structure python:context.nosy.menu(height=3)" /> 131 <span tal:replace="structure python:context.nosy.menu(height=3)" />
148 132
149 and then, like me, go and read about Zope templates. 133 for more information, go and read about Zope Page Templates.
150
151
152
153 134
154 135
155 Using Roundup 136 Using Roundup
156 ------------- 137 -------------
157 138
158
159 I got an error and I cant reload it! 139 I got an error and I cant reload it!
160 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
161 If you're using netscape/mozilla, try holding shift and pressing reload. 141
162 If you're using IE then install mozilla and try again ;^) 142 If you're using Netscape/Mozilla, try holding shift and pressing reload.
143 If you're using IE then install Mozilla and try again ;^)
163 144
164 145
146 I keep getting logged out
147 ~~~~~~~~~~~~~~~~~~~~~~~~~
165 148
166 I tried changing my password and I got 'invalid one time ticket' or something 149 Make sure that the TRACKER_WEB setting in your tracker's config.py is set
167 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 150 to the URL of the tracker.
168 Ok, so I said to use mozilla, well apparently it 'double requests' pages
169 from roundup.
170
171 This means the first request worked (ie, your request was processed) then
172 mozilla/galeon/children tried again and that request failed (ie, it tried to
173 perform an operation using a no longer valid ticket).
174
175 Dont worry, it worked. :^)
176
177 151
178 152
179 ----------------- 153 -----------------
180 154
181 Back to `Table of Contents`_ 155 Back to `Table of Contents`_
182 156
183 .. _`Table of Contents`: index.html 157 .. _`Table of Contents`: index.html
158 .. _`customisation`: customisation.html
184 159
Roundup Issue Tracker: http://roundup-tracker.org/