wish i could edit the previous post... but the styles issue was due to
the documentroot being a level below what it should have been... this
is working now using the website name as the NameVirtualHost... go
figure...
the carclubhub.com website is giving me a mod_python error, which is
expected
will do, going through now... i did find this:
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value
Go through all the Apache configuration files and find all mentions of
NameVirtualHost, Listen and SetHandler directives. Post what they are
here. If SetHandler is inside of a Location/Directory container, post
what that container directive is declared as. In turn, if they are
inside of
I have root access. I've just now attempted both moving the
NameVirtualHost *:80 around, from the python.conf to the httpd.conf,
and changed its location in the httpd.conf.
i've also moved the import for the python.conf as well, from above to
below the NameVirtualHost and there have been no
On Jan 5, 8:54 am, garagefan wrote:
> Starting httpd: Syntax error on line 1 of /etc/httpd/conf.d/
> python.conf:
> Invalid command 'xxx', perhaps misspelled or defined by a module not
> included in the server configuration
>
> it doesn't appear that anything in the is
Starting httpd: Syntax error on line 1 of /etc/httpd/conf.d/
python.conf:
Invalid command 'xxx', perhaps misspelled or defined by a module not
included in the server configuration
it doesn't appear that anything in the is being read,
but there are no errors popping up related to it. i've
Where exactly is the snippet file containing the Apache configuration
which you have added?
How is this being included into the main Apache configuration?
Try adding a syntax error into the snippet file, ie., add:
XXX
Then try and restart Apache. If it doesn't complain with an error in
i do appreciate all your assistance and am growing to understand the
server side a bit more. you're right about the documentation being...
light...
i've taken what you posted and have not seen a difference at either of
the websites mentioned the main page results in the base fedora test
page
On Jan 4, 3:11 pm, garagefan wrote:
> this is rather aggravating as i'm unsure what exactly I need to give
> you to help me :/ this isn't your fault at all, as i'm an
> unexperienced with working with servers, mod_python, python and
> django.
>
> i am learning all this
this is rather aggravating as i'm unsure what exactly I need to give
you to help me :/ this isn't your fault at all, as i'm an
unexperienced with working with servers, mod_python, python and
django.
i am learning all this as I go along.
i've got two websites on my server, both with different IP
On Jan 4, 1:39 pm, garagefan wrote:
> there is currently only one virtual host set up, for the site i'm
> working on. I do not need anything to happen with the other url.
But why are you mentioning 'site2' in one of the other posts and
seeing for it what you only
there is currently only one virtual host set up, for the site i'm
working on. I do not need anything to happen with the other url. my
django files are in a folder at the same level as the root folder of
the site.
i simply need a virtual host for www.website.net that sits at /home/
site1/ on my
On Jan 4, 12:53 pm, garagefan wrote:
> no, as then i would need to use, for example...www.website.net/mysite/*
> instead ofwww.website.net/*for the various apps.
If you are mounting it at root of web site, you should not be setting
django.root with PythonOption
i currently only have two sites, one is not being developed at this
time.. but w/o the virtual host that site displays the same apps and
info at it's url as the site i am working on, which i do not want to
happen. what i have copied for my virtual host is really everything i
have.
As i said, i
no, as then i would need to use, for example... www.website.net/mysite/*
instead of www.website.net/* for the various apps.
as i said the locations worked perfectly before attempting to create
the virtual host. right now i need to have this virtual host point to
the correct website on my server.
BTW, with mod_python, if trying to host multiple Django sites inside
of same VirtualHost, you must set PythonInterpreter directive
differently for each.
You really need to provide a more complete example showing all the
sites and how they site with respect to each other and the VirtualHost
in
On Jan 4, 12:17 pm, garagefan wrote:
> I've read the documentation, and it doesn't seem clear enough, or
> provide a fully working example?
>
> i've copied what i have in my python.conf file, keep in mind that i
> have removed site specific names and have made them
I've read the documentation, and it doesn't seem clear enough, or
provide a fully working example?
i've copied what i have in my python.conf file, keep in mind that i
have removed site specific names and have made them generic
NameVirtualHost *:80
ServerName www.website.net
18 matches
Mail list logo