>> Yes! I am in :-) . Ok.. so I owe you a few beers. Now the fun part. > >The beer is not the fun part? What strange world you must live in. > >> Now I get to figure out what to do with it :-) > >Get nadmin. > >> Thanks a million Emile. > >Don't mention it. You've shown more patience than I'd have expected. >BTW, what with your recent experience, where would we have to change >the installation instructions or data package to make it easier? I've >separated filetemplates off to a different package since these do >indeed sometimes cause confusion as most people that come from a >file-serving web experience will head for them first. > >Emile
Emile, Aside from having to patch files (which happens) I would say that a little more detail in the install documentation would be a huge plus. There were some required options that were not listed in the documentation. For example you had to define whether the install was new or an upgrade. Don't remember which module that was but the online documentation made no reference to it. There were a few cases where extra options had to be added to "configure". It just meant going into --help a few times. My guess is that whoever wrote the installation documentation had already worked with the software on a number of occasions. It wasn't exactly written for a person that had never used Midgard before. I think it made too many assumptions. The documentation seems to revolve around an install on a local machine. Are localhost installs more common than remote installs? Maybe a little more info on working around configuration changes would be a plus. Thanks again for the help, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
