Topic: 4 and loving it

[aleister]

hey guys.  i've been playing around with 4.0b and i'm digging it.  
i'm using it at home to give the roomies access over the cable line, and running a couple of web sites.  nothing beats it.  

if you have the time, i have a couple of questions:

in 3.x, we had to edit templated config files (ie, apache.conf), and then run a signal script to apply the changes.  i love the virtual domain features of 4.0, but i've noticed the the document root directory for each domain remains the same.  

now, i can make the necessary changes to the templates, but how do i implement the changes?  use signal-event? (i noticed there's a ton more actions in the new version from 3)?

or is there some better way altogether?

[Charlie Brady]

aleister wrote:

> if you have the time, i have a couple of questions:
>
> in 3.x, we had to edit templated config files (ie,
> apache.conf), and then run a signal script to apply the
> changes.  i love the virtual domain features of 4.0, but i've
> noticed the the document root directory for each domain remains
> the same.

Yep, someone else has noticed that too.

> now, i can make the necessary changes to the templates, but how
> do i implement the changes?  use signal-event? (i noticed
> there's a ton more actions in the new version from 3)?

Yep, you still need to do that. But as I said to Carl, please join the developers list, and please submit your fixes. Many hands make light work!!!

Charlie

[Joseph Morrison]

aleister wrote:
> hey guys.  i've been playing around with 4.0b and i'm digging
> it. i'm using it at home to give the roomies access over the
> cable line, and running a couple of web sites.  nothing beats
> it.  

Cool!!

> changes.  i love the virtual domain features of 4.0, but i've
> noticed the the document root directory for each domain remains
> the same.

When creating a virtual domain, you can pick which i-bay you want for the content - that overrides the document root for that virtual domain.

Let me know if this doesn't work for you!
Best regards,
- Joe

[aleister]

well, i tried creating the virtual domains using the ibays as the content, but it continues to point all my domains to the primary document root.
the virtual domains seem to be working fine for everything else (ftp, e-mail), except for the web.

i have no problems editing the httpd.conf templates to do this, except that the "/sbin/e-smith/signal-event manager-misc" script doesn't work.  says it "can't open directory /etc/e-smith/events/manager-misc."

any ideas?

-a

[Joseph Morrison]

Hello,

> well, i tried creating the virtual domains using the ibays as
> the content, but it continues to point all my domains to the
> primary document root.

Are you sure about this? This is probably a dumb question I'm about to ask, but if you're using Netscape did you make sure to hit Shift-Reload to see the refreshed page after changing the content? If you just hit "Reload" without the shift key then Netscape doesn't actually fetch the page from the server; it just renders the cached version again.

I'm not sure if Internet Explorer has an equivalent quirk.

> i have no problems editing the httpd.conf templates to do this,
> except that the "/sbin/e-smith/signal-event
> manager-misc" script doesn't work.  says it "can't
> open directory /etc/e-smith/events/manager-misc."

Hopefully you shouldn't have to edit the templates for this. The DocumentRoot should be correctly specified for each virtual domain (and overrides the main DocumentRoot setting). Do the DocumentRoot settings look right in the srm.conf file?

And yes, the manager-misc event has been split into many smaller events. In this case, you can signal the domain-modify event:

/sbin/e-smith/signal-event domain-modify

which should regenerate the Apache config files and restart the servers.

Best regards,
- Joe