Full custom httpd configuration management

[jmstacey]

I think a function that is really needed is full control over custom httpd configurations, allowing us to add/edit/delete anything we want instead of being limited to just adding configurations inside the virtualhosts.

Just my suggestion for the month

 

[jmstacey]

Or at least add to the different virtualhosts seperately instead of combined.

http://www.directadmin.com/forum/showthread.php?s=&threadid=5780

This would include seperate additions to all individual virtualhosts.
For example when adding a configuration, I might not want it to apply to all domain virtualhosts that might be there.

 

[kck]

Not only would I like separate control over SSL and non-SSL VirtualHost blocks, but also sub domains.

I envision the interface should present you with a list of VirtualHost blocks in a dropdown list and an editing area. The first entry in the list could be "apply to all" or something to that effect. As well, there would be the usual non-editable text area that shows the entire file as it currently is.

The important per-virtual-host bits could be one |PIPEREPLACE| variable that's associated with the appropriate /usr/local/directadmin/data/users/*/virtualhosts/sub.domain.conf

Thoughts?

 

[midan]

Editable user httpd.conf

Hello,

I just wanted to mention that I am eager to get this feature as well. I have to freeze the /usr/local/directadmin/data/users/<user>/httpd.conf file for a few accounts because of specific needs.

But what if one of these users want to add new subdomains? DA won't be able to configure it's VirtualHost...

And then it gets a little complicated because you have to grant permissions to the user's httpd.conf file, allow the user to add it's subdomain and then reapply the changes to the user's httpd.conf file and freeze the file again.

Please let us know what your plans are on that one.

Thanks a lot!

 

[Chrysalis]

nice timing bringing this up, biscally I need to map a subdomain but can't do it the normal way since DA hits an error creating the dir which was caused by a symlink I made to work around another issue for the user, DA of course aborts when it hits an error instead of just warning something went wrong, so that stopped me adding the subdomain. I then setup the DNS record and tried to add the vritualhost container in the custom httpd bit but that isnt allowed and I couldnt get it working so I am going to have to modify manually in the shell and forbid DA access to write to the file so it doesnt revert my changes.

 

[vertangie]

When Apache applies changes

And while were at it.

Could we choose when to have apache restart to apply changes.

I can't quite work out when it's happening and I've got 14 Custom HTTPD Configurations to update this afternoon.

I'd rather have apache restart when the whole lots done and not before.

It crashed my server earlier today after doing 3 of them. It's a real limitation in my view.

Angie

 

[squirrelhost]

think i mentioned it before, but we could someday have

/usr/local/directadmin/data/templates/

/usr/local/directadmin/data/templates/custom/

and

/usr/local/directadmin/data/templates/custom/<user>/

with the order of search/process going backwards
up this list, or what have you. no point in limiting
customisation to only the httpd.conf file ..

 

[ju5t]

Any updates on this?
We basically need it for several subdomains, freezing the file is not a solution if you ask me.

 

[wheatgrass]

Or at least add to the different virtualhosts seperately instead of combined.

http://www.directadmin.com/forum/showthread.php?s=&threadid=5780

This would include seperate additions to all individual virtualhosts.
For example when adding a configuration, I might not want it to apply to all domain virtualhosts that might be there.

Is this feature already implemented and if yes, please advise how to access it. Thanks.