mharc-users

Re: mharc "user" and Getting Started

2003-08-02 16:02:33
On August 2, 2003 at 14:16, Vicki Brown wrote:

If other parts of the installation guide referenced that name again, I'd
understand the connections. If, for example, the sample directory used was
/home/mailarch/archives...

A good suggestion.  The install guide is not consistent with the example
account name used.

Is the (unstated) recommendation to use the "Pathname to install mharc" as
the homedir for this account?

mharc can be installed anywhere, but under the user account is typically

so it is recommended to create a user account (not specifically stated in
docs, only implied)

The implication is fairly direct when the doc states:

  NOTE: You should be logged into the archive account when installing
        mharc.

Now, if the requires the creation of an account, or the use of an
existing account, that is up to the user.

Wherever you install, you
will need to make sure that your web server has access to the mbox and
html locations so people can access the pages and make sure to edit
config.sh to properly reflect file path and URL locations.

Is this specified in the docs?

Yep, under "Configuration Check".  It states to examine lib/config.sh
and make any edits as needed.  There is an assumption that the user
will check the comments and each variable in the file.

Let me be more clear. I didn't ask if I must have multiple users but if I
_could_ have multiple users.  That's orthogonal to need; that's "desire".

I do not understand your question.  Are you refering to people who
access the archives via the web or are you talking about mharc users
(i.e.  the admins)?  If the former, the answers is obvious since the
archives are web pages and access is a web server issue.  If the
latter, you can have separate installations of mharc on the same
system if you choose.  I think this would be rare for an individual
mharc user, but more common in an environment of multiple users that
use mharc.

OK, so it appears that I am recommended to
   1) create a user, fred (mailarch, mharc, marcV, whatever)
   2) give that user a home directory
   3) use that home directory (o0r a subdirectory of it) as SW_ROOT
   4) get mharc configured
   5) subscribe my user (fred...) to the desired mailing lists

These steps seem to be missing (explicitly) from the docs; if I simply missed
seeing them, I would appreciate a pointer to their location.

These explicitly steps are not mentioned, but can be implied.
Some steps may not be relevant for some users.  (1) may or may not
need to be done.  For example, mharc may be used under and existing
account, which would be common for ISP-provided accounts that provide
shell access.  Mharc does not make the assumption that the user has
root priviledges, and in actuality, it is designed to be installed
and used by non-root users (plus, the docs caution about using
mharc as root for security reasons).

(2) has to deal with user account creation, and this outside the
scope of mharc.  (3) is one way to configure things.  Typical usage
would have mharc installed somewhere under the user's home directory
and not directly in the home directory.

For example, I
don't see anything about how to USE mharc from the web :-(

mharc does not have a web-based administration interface.  All admin
functionality is currently done from the shell.

I didn't say I can't figure out how to administer it. I can't figure out how
to use it. There are all sorts of cgis in a subdir oof $SW_ROOT. How do I use
them? What are they for? What's the "Getting Started" example? How do I run
things and make a page on the web? How do I find and access that page?

There is a section called "Web Server Configuration" on how to configure
the web server.

The only thing missing in the docs in the issue about configuring
the server so that the ROOT_URL in config.sh actual works.  If mharc
is installed under a web accessible directory, you are good to go (an
example would be installing it under the public_html directory of the
archive user account).  If not, the server will need to be configured.
Basically, defining an Alias directive should be sufficient.

All the CGI related configuration should already be handled by the
etc/apache.conf template provided.

--ewh

---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHARC-USERS

<Prev in Thread] Current Thread [Next in Thread>