I would like to setup the ability that each user created has a static ip, and is assigned their own instance of apache. Allowing them to configure mod_perl on the fly or mod_python and being able to restart or hup the process. Is anyone currently doing this with DA?
Per user instances
- Thread starter welch
- Start date
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,334
And you realize of course only one instance can listen on port 80. All the others will have to listen on different ports and anybody trying to get to the users' domains will have to specify the port number in the url like http://www.domain.com:8080 http://www.domain2.com:8081 http://www.domain3.com:8082 and so on.
I think you want to rethink your approach. If you really want each user to have their own apache then they probably need their own vps.
Eh, this wouldn't happen. Each user would get a static ip as mentioned, and adding additional domains would be virtual hosts. But this allows them to modify mod_* information without affecting other users. The main conf sits outside the directory, so I can limit its growth, but the additional confs get included.
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,334
I would like to see a working example of what you are talking about. I don't think what you are talking about can be done. But read my sig.
But if you can do it with just some configuration changes then by all means edit the user templates and do it.
But if you can do it with just some configuration changes then by all means edit the user templates and do it.
jlandes
Verified User
Can the Custom HTTPD Configurations option in the admin panel do some of what you are looking for?
If this ability could be extended to the users. It would be a large rewrite of DA to make this happen, and this i understand. Basically what I have setup manually is a custom init file for httpd. I will start up different apache processes each with their own self conf file each with a different listen IP. This allows them to run on port 80 on different ips.
So, essentially, when a new user is created in da, it adds a new generic conf group files to say /home/user1/apache_conf
in /home/confs/user1.conf << will have listen, fork information, the goodies
then in DA have the option to edit the /home/user1/apache_conf and also restart apache, BUT only for its instance
is this making sense? Or should I ask. How are other people setting up Django, Ruby, Perl applications for their clients? I hope not manually?
nobaloney
NoBaloney Internet Svcs - In Memoriam †
To clarify for Floyd,
Yes you can set up apache to run on only one IP#.
And then you could have multiple apache instances running on port 80. The limit is per port per IP#.
To clarify for welch,
We offer our clients the ability to run perl applications, and we have no problem running them the way DirectAdmin is currently set up. We do NOT currently support any of the others you mention.
What you can easily do is can make rather complex changes to the user-specific html include files, and chattr them so DirectAdmin can't overwrite them. If you want more, then you may be able to figure out how to do what you want within DirectAdmin but it's probably not a good choice, since DirectAdmin just wasn't designed for what you're writing about. In that case, then VPS would probably be a good way for you to go.
Jeff
Yes you can set up apache to run on only one IP#.
And then you could have multiple apache instances running on port 80. The limit is per port per IP#.
To clarify for welch,
We offer our clients the ability to run perl applications, and we have no problem running them the way DirectAdmin is currently set up. We do NOT currently support any of the others you mention.
What you can easily do is can make rather complex changes to the user-specific html include files, and chattr them so DirectAdmin can't overwrite them. If you want more, then you may be able to figure out how to do what you want within DirectAdmin but it's probably not a good choice, since DirectAdmin just wasn't designed for what you're writing about. In that case, then VPS would probably be a good way for you to go.
Jeff
Jlasman,
Thank you. I currently do these setups manually, but i think since no other options are out there, in DA 2 this could be a field that is growing, for a premium of hosting, and will fit the bill perfectly. Cmon.... wanna be the first control panel that supports advanced web development... or hell... web design of today. Python, Ruby, and Mod_Perl is the way of future apps.
hostpc.com
Verified User
And on the 8th day, God created VPS's
heh, Wouldn't it be nice to offer customers a manage solution without telling them "Get a VPS". Seems like a lazy man shortcut. I believe per user instance will work alot better than a vps, actually cost and time compared it would be.
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,334
Yes it would and I am still waiting for you to tell us how to do that. If you told me how to make the configuration changes then I could probably write something to get DA to do it. But until I get some details I guess there is nothing more to talk about.
Floyd, ill give ya the basics, if you need copies of each file in question, i will be more than willing to send them your way.
When a new user wants on, i do the following setups.
I added the domain to a /etc/serverslist file that I have created in junction with a custom init so i can do service httpd start <domain>
After I add the domain to the serverslist, i then go ahead and make them a home directory. within that home directory, i put a folder called apache_conf. From apache_conf, is a <domain>.conf file that has all the virtual host information in it.
I then setup a pythonpath for that user so that any python installations will reference their path.
I then start the apache up by again service httpd start <domain>
Its really simple, but to automate the generation of email, databases, and the other 'web' stuff is whats a pain.