Access http://localhost:7080/ (or whatever you configured) anonymous
or http://localhost:7081/ with user name "gonzo" password
- Better keep it on a terminal to watch log output for now.
- Start with understanding the applications in the "app" directory.
Exploring the system inside (only recommended if you need to debug
the server, not your applications - but "sparse" error messages might
still force app developers to know how to do it):
$ telnet <host> 7070
(The number 7070 is the "Control Port" defined in the
config file and controlled via the system control panel.)
See the prompt ";; Nu". Type valid scheme expressions at the
next line. Be careful, doing so might corrupt your data base if
you accidentally keep references to objects in the data base over
garbage collection time in the persistent store. If you don't
understand what I'm talking about: just explore it but refrain
from modifying the data base and you're safe.
You M U S T N O T run the debug access at any production system!
you definitely don't want to do that, it breaks each and every
Useful command on the debug console:
||log more warnings and include stack trace with exceptions
||lambda (OID this message result)
||traces AskemosDVM step by step through the procedure.
- (X)Emacs uses want to customize wiki-remote (see SystemRequirements)
it really eases the edit/test cycle.
xemacs+wiki-remote are not SSL aware.
As a work around it is recommented to use ssh port forwarding with