3 Modes of deployment
When installing Schtonk the following things need to be taken care of
When all these are satisfied, the fire up your browser asking for
and you should get yourself to the zero-page of schtonk. This obviously
varies depending on how you did your web server configuration. If you did
install the debian package available for download, it installs such
apache2 config that the correct URL is http://your.ser.ver/schtonk/g.tcl. Installing schtonk does
not enable https access to web server automatically, encryption keys etc.
still need to be put in place manually.
- There needs to be MySQL db containing tables defined in file
tables.sql that is included in schtonk distribution.
- backend.tcl needs to be running e.g. someone needs to say
`tclsh backend.tcl' and this may very well be some script
in /etc/init.d/somewhere. backend.tcl needs to know how to
connect to MySQL ; default db schema name is schtonk and
default db username is schtonk with no password ; you may want
to change that, just look at beginning of file backend.tcl.
- g.tcl needs to be copied to such a directory that when http
client issues HTTP GET with /cgi-bin/schtonk/g.tcl then
the g.tcl is hit. Actual location of this directory depends
on your web server configuration. Examples will be given
later. g.tcl will be linked to multiple names with command
`ln', each re-presenting different kind of request
- httpd needs to be running.
pages are not referred with names but instead with numbers.
Another note is that while schtonk as installed from debian package has
minimal lsb-tags support in /etc/init.d/schtonk file, not all sites have
the feature turned on so users should be careful to check both apache and mysql
are running prior to startup of schtonk.