/[gnumed]/gnumed/gnumed/client/doc/TODO/user-manual.txt
ViewVC logotype

Contents of /gnumed/gnumed/client/doc/TODO/user-manual.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.25 - (show annotations) (download)
Wed Apr 2 11:10:05 2003 UTC (21 years ago) by ncq
Branch: MAIN
Changes since 1.24: +24 -1 lines
File MIME type: text/plain
- added blurb about use of "script" during bootstrapping

1 # $Source: /cvsroot/gnumed/gnumed/gnumed/client/doc/TODO/user-manual.txt,v $
2 # $Revision: 1.24 $
3 ---------------------------------------------------
4 Rules:
5 ------
6 - add material for the User Manual in this text file if you
7 don't want to edit the sgml code yourself
8 - leave behind an email address
9 - delete things if you incorporated them into the manual
10 - please date it.
11 Thanks
12 ---------------------------------------------------
13 Karsten.Hilbert@gmx.net Mit 05 Feb 2003 14:25:17 CET
14
15 Belongs into Admin->Config:
16
17 Upon startup the client autoconfigures the language used
18 in the database.
19
20 The following things influence its decision:
21
22 The language is taken from the system locale in the environment
23 variables checked for the GUI language by gmI18N.py.
24
25 If there's no i18n_curr_lang table in the database the client
26 assumes that no translations are wanted and tries to work
27 without it. Same if other errors prevent normal operations - a
28 warning is logged and things continue.
29
30 If the language given in the database doesn't match the system
31 locale the user is asked whether to update the database setting
32 to that. One can influence the system locale setting in
33 per-instance wrapper scripts if so desired.
34
35 The database language setting is only updated if translations
36 are actually available for the target language. Two levels of
37 truncation of the system locale are used to find matching
38 translations:
39
40 1) full locale: 'de_DE@euro'
41 2) no dialect: 'de_DE'
42 3) no country: 'de'
43
44 This allows for a missing Austrian translation to fall back to
45 a general German (de_AT -> de) one, for example.
46 ---------------------------------------------------
47 I looked up the syntax in gmCfg.py, but could I suggest that a line be
48 inserted in the bootstrap_gm-db.py file which says something like
49
50 #before running this script:
51 #
52 #-make sure you've installed the symbolic links as listed in make-links.sh
53 # you can run this by typing sh make-links.sh
54 #
55 #-make sure you check the section:
56 #language library dirs = $language library dirs$
57 #to make sure the pathways point to the pgsql libraries
58 #
59 #usage :
60 # python bootstrap_gm-db.py --conf-file=yourconfigfilenamehere
61 # e.g bootstrap_gm-db.py --conf-file=bootstrap-standard_AU.conf
62 #
63
64 Anyway, I can now get up the interface at work, so perhaps having struggled
65 twice to do this the third time (when I get my dead machine at home back)
66 it'll be relatively easy. when I do I'll keep a line by line instruction set
67 to add to the installation docs.
68
69 Regards
70
71 Richard
72
73
74 _______________________________________________
75 Gnumed-devel mailing list
76 Gnumed-devel@gnu.org
77 http://mail.gnu.org/mailman/listinfo/gnumed-devel
78
79
80 ---------------------------------------------------
81 michael.bonert@utoronto.ca Wed Apr 2 00:17:07 EST 2003
82 ICQ ID: 97418709
83
84 GnuMed Install Instructions for Mandrake Linux 9.1
85 by Michael Bonert
86
87 1. Install CVS (from the Mandrake CDs):
88 cvs-1.11.5-1mdk
89
90 2. Install postgresql (from the Mandrake CDs):
91 postgresql-7.3.2-5mdk
92 postgresql-devel-7.3.2-5mdk
93 postgresql-python-7.3.2-5mdk
94 postgresql-server-7.3.2-5mdk
95 postgresql-pl-7.3.2-5mdk
96
97 pgaccess-0.98.8.20030117-2mdk # nice to have
98 postgresql-docs-7.3.2-5mdk # nice to have
99
100 NOTE: If the packages all show up when you do a
101 'remove software packages' (in 'mcc') they are all
102 installed.
103
104 3. Install wxPython -- (version used: wxPythonGTK-py2.2-2.4.0.1-1.i386.rpm)
105
106 4. Install mx extenstion libraries -- (egenix-mx-base-2.0.4-py2.2_1.i386.rpm)
107
108 5. Install pyPgSQL -- (pyPgSQL-2.3-1.src.rpm)
109
110 Before building and installing pyPgSQL make sure you have the following
111 (from the Mandrake CDs):
112 libpython2.2-devel-2.2.2-6mdk
113
114 $ tar zxvf pyPgSQL-2.3.tar.gz # gunzip + untar 'pyPgSQL-2.3.tar.gz'
115 $ cd pypgsql
116
117 Set include and library directories in "setup.py" with your favourite editor:
118 ---
119 # Set this to 1 if you need to use your own settings
120 USE_CUSTOM = 1 # Don't forget to change this line!!!
121
122 ...
123
124 if USE_CUSTOM:
125 include_dirs = ["/usr/include/pgsql"]
126 library_dirs = ["/usr/lib/pgsql"]
127 ---
128 $ python setup.py build
129 $ python setup.py install
130
131 NOTE: If the directory settings in 'setup.py' are wrong you get a misleading error about 'gcc'
132
133 Testing pyPgSQL:
134 $ cd test # install directory: ../pypgsql/test
135 $ python PgSQLTestCases.py
136
137 OUTPUT:
138 ..................................................................
139 ----------------------------------------------------------------------
140 Ran 66 tests in 1.090s
141
142 OK
143
144
145 6. Get GnuMed source
146 RECOMMENDATION: install gnumed in "/home/your_user_name/"
147 -- where 'your_user_name' is your favourite normal user - e.g. 'michael'
148
149 $ cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/gnumed login
150 $ cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/gnumed checkout gnumed
151
152 7. Modify postgresql.conf
153 $ su
154 # cd /var/lib/pgsql/data
155 # vi postgresql.conf
156 change '#tcpip_socket=false' to 'tcpip_socket=on'
157
158 8. Modify "pg_hba.conf" found in "/var/lib/pgsql/data"
159 # vi pg_hba.conf
160
161 last part of our "pg_hba.conf" should look like this:
162 ---
163 # Using sockets credentials for improved security. Not available everywhere,
164 # but works on Linux, *BSD (and probably some others)
165
166 #local all all ident sameuser
167 local all all trust
168 host all all 127.0.0.1 255.255.255.255 trust
169 ---
170
171 9. Create db
172 (see -- http://mail.gnu.org/archive/html/gnumed-devel/2003-02/msg00079.html)
173 $ su root
174 # passwd postgres # change password (I don't know what the default is--
175 # you'll need this password later so remember it.)
176 # su postgres
177 $ createuser your_user_name # in my case: "createuser michael" (answer 'y' to both questions)
178 $ createuser _your_user_name # in my case: "createuser _michael" (answer 'y' to both questions)
179
180
181 (as normal user)
182 $ cd /home/your_user_name/gnumed/gnumed/server/bootstrap
183 $ cp bootstrap-standard-AU.conf.sample your_user_name-db.conf
184 $ ln -s /home/your_user_name/gnumed/gnumed/client/python-common modules
185 $ ln -s /home/your_user_name/gnumed/gnumed/server/sql/ sql
186
187 At this point you may want to confirm that postgresql is running:
188 $ mcc
189 click on 'System'
190 click on 'DrakXServices...'
191 'postgresql' should say 'running'
192
193 $ python bootstrap-gm_db_system.py --conf-file=your_user_name-db.conf
194 When prompted:
195 - yes
196 - give password
197 - give another password
198
199 NOTE: If you have problems the log file is in: "/home/your_user_name/.bootstrap-gm_db_system"
200
201 10. set 'GNUMED_DIR' variable
202 $ cd # cd to home
203 $ vi .bash_profile # or your favourite text editor
204
205 Add the following:
206 ---
207 GNUMED_DIR=$GNUMED_DIR/home/your_user_name/gnumed/gnumed/client
208 ---
209
210
211
212 Running GnuMed:
213 $ cd /home/your_user_name/gnumed/gnumed/client/wxpython
214 $ python gnumed.py --debug
215
216 Find something you don't like and fix it... ;O)
217
218 ---------------------------------------------------
219 Karsten.Hilbert@gmx.net 2.4.2003
220
221 there are two options for you:
222
223 1) connect to the public database on my server for testing the frontend:
224 server: anubis.homeunix.com
225 database: gnumed-public
226 user/password: please write me a private mail
227
228
229 2) on bootstrapping:
230
231 To capture even the last bit of screen output do this:
232
233 - go to the directory where you want to start bootstrap*
234 - run the command "script -a bootstrapping.log"
235 - run the bootstrapping as you did before
236 - when finished, type "exit"<enter>
237 - now also send me the bootstrapping.log file
238
239 Michael: Can we add the latter part to the installation
240 instructions ? Thanks for your excellent work !
241
242 --------------------------------------------------

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26