|
I have created a private instance in apache, following the directions here: https://community.webfaction.com/questions/14339/installing-a-private-instance-of-the-shared-apache Now I want to create a new directory in my webapps folder that a new virtual host in my private apache instance will point to. However, permission is denied when I try to make a directory here. Should I instead be creating a new app in the control panel which will create the directory for me? However what kind of app should I choose? If I choose custom app, webfaction will try to give me a new port. But I don't need a new port because I already have a port assigned to my private instance of apache. Should I create a static app instead? If I do this just to create a new directory should I point the domain name at the custom app connected to the private apache instance or to the static app created just to create a new directory in my webapps folder. thanks for your help. asked 20 Jan '14, 21:26 Geoff16W |
|
The directories in the webapps directory can only be created from the creating applications in the control panel. However, you don't have to do that. You can create a directory structure in the root of your home directory for your applications and just point your apache configuration to that location instead of to something in the webapps directory. answered 20 Jan '14, 21:43 bmeyer71 ♦♦ Hmm, ok - but what's the proper way to associate domain names with this directories in other applications -- I've pointed to httpd.conf file to the webapps-custom/project but it is still pointing to the directory created in the original webapps/ directory
(20 Jan '14, 22:16)
Geoff16W
Since you are using a custom Apache install, you would just create new website entries add the domain name you want and assign your Apache application to it. Then you would configure your domain in your httpd.conf to point to your application directory.
(20 Jan '14, 22:23)
bmeyer71 ♦♦
ok - last question -- does my private_apache directory need to be within he directory of the custom app? So something like ~/webapps/customproject/private_apache -- right now i have the private_apache in the ~/ and the conf file is not directing to my webapps-custom/ but instead it continues to go to ~/webapps/customproject
(20 Jan '14, 22:32)
Geoff16W
Perhaps I should have understood $HOME in the example as the customapp directory rather than the actual $HOME path on the server??
(20 Jan '14, 22:36)
Geoff16W
No. The actual install does not have to be in webapps. You can just create the "Custom app listening on port" application type to reserve the port for your Apache instance to listen on.
(20 Jan '14, 22:37)
bmeyer71 ♦♦
erg well somethings not working: http://plaoul.jeffreycwitt.webfactional.com/ http://wodeham.jeffreycwitt.webfactional.com/ If you have time check out both those links - both of those domains are pointing to the directory that the private_apache is contained -- not the document roots I specified in the httpd.conf file
(20 Jan '14, 22:52)
Geoff16W
nevermind -- I'll start a new question for my problem. Thanks for your help.
(20 Jan '14, 23:15)
Geoff16W
showing 5 of 7
show 2 more comments
|
