HP3000-L Archives

March 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Fri, 17 Mar 2000 11:16:04 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Donna Garverick wrote:
>
> hi all~
>
> we're taking our first baby steps for placing apache into
> production and i've got some questions....  how are other
> sites allowing various application groups to tie into
> apache?  that is, on my crash-n-burn system, i've been
> modifying the ../htdocs/index.html file to hook in different
> things.  that's fine for just me, but not in production.
> are you doing something like
> http://your.system/~MGR.<account>/?  that's quite doable but
> it seems a bit unsophisticated to me.  of course, i
> certainly don't want folks literally placing files in the
> apache account -- so what's the trick here?  links, i should
> think, but...?             - d

The way I handled this when I was webmastering for www.cccd.edu was to have the
users create their own content in their public_html/ subdirectories, and then
test it via:

http://hostname/~username/content.html

When they were satisfied, and I was satisfied, I then created a symlink in the
DocumentRoot directory to point to the user's public_html/ subdirectory.  So
then the user could then publish their URL as:

http://hostname/symlinkname/content.html

So the cumbersome ~username syntax would no longer be necessary.

- Mark B.

ATOM RSS1 RSS2