[Booki-dev] Problems with spellchecker

Lachlan Musicman datakid at gmail.com
Wed Feb 9 15:17:07 PST 2011


James,

When I was referring to the site.conf details, the entries below was
what I meant.

Traditionally http.conf would hold the "apache" configurations, just
as php.conf holds the php configuration.

There is no need to change your set up, but if you have a lot of sites
running, http.conf can get messy, so moving the virtual host entries
to files things like booki.conf helps keep your conf files cleaner.
Just FYI

Cheers
L.

On Thu, Feb 10, 2011 at 08:59, James Simmons <nicestep at gmail.com> wrote:
> Tuuka,
>
> These are my virtual host entries in httpd.conf:
>
> <VirtualHost 10.239.17.123:86>
>        # ServerName booki.walgreens.com
>        ServerAdmin jim.simmons at walgreens.com
>
>        DocumentRoot /home/jds/src/booki/
>
>        <Directory /usr/share/pyshared/django/contrib/admin/media/>
>        Order allow,deny
>        Allow from all
>        </Directory>
>
>
>        <Location "/">
>
>            SetHandler python-program
>            PythonHandler django.core.handlers.modpython
>            SetEnv DJANGO_SETTINGS_MODULE booki.settings
>            PythonDebug On
>            PythonPath "['/home/jds/src/booki/lib'] + sys.path"
>
>        </Location>
>
>        <Location "/favicon.ico">
>            SetHandler None
>        </Location>
>        <Location "/media">
>            SetHandler None
>        </Location>
>
>        Alias /favicon.ico /home/jds/src/booki/favicon.ico
>        Alias /media/ /usr/share/pyshared/django/contrib/admin/media/
>
>        ErrorLog /var/log/apache2/booki-error.log
>
>        # Possible values include: debug, info, notice, warn, error, crit,
>        # alert, emerg.
>        LogLevel warn
>
>        CustomLog /var/log/apache2/booki-access.log combined
>        ServerSignature On
>
> </VirtualHost>
>
> <VirtualHost 10.239.17.123:80>
>        ServerAdmin webmaster at localhost
>        #XXX set server name
>        #ServerName objavi.halo.gen.nz
>        # limit MEM to 800 million bytes
>        RLimitMEM 800000000
>
>        #Sometimes it takes a while. Wait.
>        TimeOut 600
>
>        DocumentRoot /home/jds/src/objavi2/htdocs
>        <Directory />
>                Options FollowSymLinks
>                AllowOverride None
>        </Directory>
>        <Directory /home/jds/src/objavi2/>
>                Options +All +ExecCGI
>                AllowOverride None
>                Order allow,deny
>                Allow from all
>                AddHandler cgi-script .cgi
>                # Remove output filters in case mod_deflate is being used.
>                RemoveOutputFilter .cgi
>        </Directory>
>
>        DirectoryIndex index.html objavi.cgi
>        ErrorLog /var/log/apache2/objavi-error.log
>
>        # Possible values include: debug, info, notice, warn, error, crit,
>        # alert, emerg.
>        LogLevel debug
>
>        CustomLog /var/log/apache2/objavi-access.log combined
>        #ScriptLog /tmp/objavi-cgi.log
>
> </VirtualHost>
>
> The first one is for Booki, the second for OBJAVI 2.  I discovered
> that OBJAVI does not like to run on anything other that port 80, but
> Booki seems to be more flexible.  I would definitely like to run both
> on port 80 on a single box with different subdirectories.
>
> Thanks,
>
> James Simmons
>
> On Wed, Feb 9, 2011 at 3:46 PM, Tuukka Hastrup <Tuukka.Hastrup at iki.fi> wrote:
>> James Simmons wrote:
>>
>>> http://howtoforge.com/installing-apache2-with-php5-and-mysql-support-on-fedora-13-lamp-p2
>>
>> Ok, good to know .php files *are* working on your server - I misunderstood.
>>
>>> I have two virtual hosts on my Apache install.  One is running on port
>>> 86 and is for Booki.  The other one is on port 80 and is for OBJAVI 2.
>>>  When I put the info.php file in the document root for OBJAVI 2 it
>>> works fine.  When I put it in the doc root for Booki I get 404 with a
>>> Django error page.  Django is loading image files and other stuff from
>>> that directory, but it seems to be interfering with running PHP.
>>
>> The Django error page is an essential clue: this tells me there's a
>> problem in what paths are configured to be served by Django. You need to
>> tell Apache to not pass that path to Django, as Django won't run PHP.
>> How have you configured Apache to pass the paths to Django?
>>
>>> I really need to run Booki and OBJAVI on the same server.
>>
>> I hope it will be possible to run them both on port 80 on the same
>> server. I have published patches required to run Booki on a subdirectory
>> instead of the server root, waiting to be merged to official versions of
>> Booki, here: https://github.com/tuukka/booki/commits/script-name
>> _______________________________________________
>> Booki-dev mailing list
>> Booki-dev at lists.flossmanuals.net
>> http://lists.flossmanuals.net/listinfo.cgi/booki-dev-flossmanuals.net
>>
> _______________________________________________
> Booki-dev mailing list
> Booki-dev at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/booki-dev-flossmanuals.net
>



-- 
Crunchiness is the gustatory sensation of muffled grinding of a
foodstuff. Crunchiness differs from crispiness in that a crispy item
is quickly atomized, while a crunchy one offers sustained, granular
resistance to jaw action. While crispiness is difficult to maintain,
crunchiness is difficult to overcome.
from The Best of Wikipedia http://bestofwikipedia.tumblr.com/



More information about the Booki-dev mailing list