[Booki-dev] Problems installing Booki on Fedora 11

[James Simmons]

Aleksander,

I figured out how to use Booki from a machine other than the one it's
on.  You need to run

./manage.py runserver ipaddress:port

otherwise it is bound to 127.0.0.1:8000.

Now I have another issue: OBJAVI.  I cannot use the public OBJAVI.
For one thing, sending books to it doesn't work.  I see a thermometer
going across as if the book was being sent *somewhere* and there is a
link shown afterwards, but clicking on the link just says the book is
not on objvai.flossmanuals.net.  Even if it did work we don't want
confidential company publications to go to a public server.  We need
our own OBJAVI.

We don't need anything to import books.  Copying and pasting from our
current MediaWiki does just fine.  But we do need OBJAVI and probably
the export to HTML used by the FM site as well.

James Simmons


On Wed, Oct 13, 2010 at 9:29 AM, James Simmons <nicestep at gmail.com> wrote:
> Aleksander,
>
> I don't know that we'd actually use ORACLE here, but I wanted to try
> it.  We have some executive blogs that use MySQL so I could probably
> use Postgres here too.
>
> I was able to get Booki up and running on Fedora 13 using sqlite3 at
> the office.  Unfortunately, I can't connect to port 8000 from any
> machine other than the one it's installed on.  I've disabled the
> Fedora firewall and turned off SELinux and still no good.  The obvious
> answer is to install on port 80 using WSGI, but the docs aren't
> totally clear to me.  A well-commented sample .wsgi file would be a
> worthy addition to the project.
>
> The key line in that file would be this:
>
> os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'
>
> I can't figure out what is supposed to go where 'mysite.settings' is.
>
> Another issue I have is connecting to Git from the office.  We deal
> with a proxy server and lots of firewalls here, so using git:// isn't
> going to work for me.  If I could use http:// instead that would be a
> great help.  What I ended up doing was downloading at home and burning
> the directory to a CD.  That won't help me to get the latest code, of
> course.
>
> James Simmons
>
>
> On Tue, Oct 12, 2010 at 5:45 PM, Aleksandar Erkalovic
> <aerkalov at gmail.com> wrote:
>> hi,
>>
>> well.. good luck with oracle! i don't like the idea, i work as ibm
>> informix consultant, and oracle
>> is the bigger and muuuuuuuuch more popular enemy :) there is only
>> couple of places with
>> raw sql. django does not have support for JOINS.. so maybe, that is
>> something what will
>> have to be manualy changed. other then that, for now, i think there
>> should be no problems
>> (except some constraints on the user types). please tell me how you
>> are going with it, i
>> will try to help you as much as i can [i tried to install oracle
>> express once, but i did not have
>> 1 (point something) GB of swap for it to work]  also, consider
>> switching to ibm informix at work.
>> i could get you very good discount :)
>>
>> aco
>