Dan Hammer wrote:

> Aside from having to patch files (which happens)

Well the patch wasn't really necessary... in the beginning I figured
you specifically _wanted_ filetemplates, and that did require the patch.

> 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.

Ah yes. The data package has seen huge changes since the docs were
last updated.

> 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.

*grin* A fair assumption. Which points out the problem I posted about
yesterday (in a different thread): as a developer, it's hard to write
end-user documentation because things become obvious to you if you
build them yourself.

My father-in-law has been into carpentry as a hobby for probably
longer than I've lived. Given his 'exhaustive' instructions,
I couldn't build a simple bookcase, because he tends to leave
out important stuff ("_of course_ you need ... inch nails. And
are you _serious_ you want to use _that_ wood?" 'but you said to
get 'some nails and wood') which he has internalized.

> It wasn't exactly written for a person that
> had never used Midgard before.

as it wasn't written _by_ a person that had never used Midgard before.
Not an excuse (and certainly not an accusation), just an observation.

> I think it made too many assumptions.

:) And so did we.

> 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.

OK. The default install sets up local-access-only for two reasons:
1) localhost is a safe guess (will most likely work unless you've
   screwed with your system).
2) localhost is a safe default; since the default password is well
   known, at least 'localhost' limits potential culprits to those
   having shell access to your server.

But I totally forgot you could have used --with-host=www.myautomd.com and
--with-port=8101 and things would have worked. I've updated the data
package INSTALL file.

Emile



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to