[FM Discuss] installation procedure

[James Simmons]

Claus,

You and I are in the same boat, more or less.  I can't get OBJAVI to
work with my local copy of Booki either, but I know some of the
reasons.

First, in spite of what the Booki docs say you WILL need your own
OBJAVI.  There is a file config.py in OBJAVI that has an array named
SERVER_DEFAULTS which needs to have an entry for every server that
OBJAVI works with.  Since your server at home isn't in that table it
uses a default value which won't work.

If you have your own OBJAVI you can add an entry to this table using
the ip address and port of your own Booki as an entry name.  Be sure
to copy the 'booki.flossmanuals.net' entry.  The one named LOCALHOST
won't work unless you change the 'interface' value to Booki.  (Even
then it won't work, but it will be better).

If you're installing OBJAVI on Fedora you will want to disable SELinux.

I have the impression that Booki as it now exists only works on the
booki.cc server.  It isn't ready to install elsewhere yet.  I'm hoping
that the developers will try and install it on another computer and
document or resolve the problems that come up.  Right now there are
too many loose ends in the instructions.

James Simmons


On Tue, Oct 26, 2010 at 4:07 AM, Claus Denk <denk at us.es> wrote:
> On 10/26/2010 01:02 AM, Aleksandar Erkalovic wrote:
>>
>> Hi Claus,
>>
>>
>>>
>>> 1) manage.py would miss module sputnik. I have copied the sputnik dir
>>> into
>>> the /lib/booki dir and changed "sputnik" to "booki.sputnik" in
>>> settings.py,
>>> this worked. I have probably some path setup incorrect?
>>>
>>
>> you can find file env.sh.original in repository. You can copy it to
>> env.sh and with
>> ". ./env.sh" load before running Booki (good while doing development or
>> just
>> testing. You don't have to define global setup or define this every
>> time you want to
>> start booki). You should have in PYTHONPATH your "booki/lib/"
>> directory. Also, you
>> should define environment variable DJANGO_SETTINGS_MODULE=booki.settings.
>>
>> If you tried to install booki with pypi before you might have problem.
>> Pypi installed it
>> under /usr/lib something and we changed structure of modules in newer
>> version.
>> Before it used to be "booki.sputnik", but now it is "booki" and
>> "sputnik" as two modules.
>> If you only used latest source from git repository you should not have
>> this problem.
>>
>
> Thank you very much, editing env.sh and "source env.sh" solved my config
> problem.
>
>>
>>>
>>> 2) With sqlite it seemed to work now, but when trying to use mysql as a
>>> database, I get
>>> Error: One or more models did not validate:
>>> editor.book: "url_title": CharField cannot have a "max_length" greater
>>> than
>>> 255 when using "unique=True".
>>>
>>
>> I will check this with MySQL. We use PostgreSQL, but you can use
>> sqlite also (hard to do
>> schema upgrades with sqlite, when doing upgrades). Right now, there
>> are only couple of
>> places where we use raw SQL (because Django ORM does not support
>> JOINS), so support
>> for MySQL is possible.
>>
>> Also, probably it is not very smart to have unique url title longer
>> then 255, i changed that in
>> hurry for one event, because while doing import of archive.org books i
>> realized their titles
>> can be extremely long. Will look into this.
>>
>
> I changed the field length from 2500 to 250 in the model and now it works
> with mysql.
>
> I have one Problem persisting: I am not able to export to objavi. When
> pressing "Publish this book", the status bar "Your books is being sent to
> Objavi  ..." (should be "book", shouldn't it?) is advancing, but when it is
> apparently finished, nothing happens. Where is the exported book supposed to
> be stored? Or do I have to install my own version of objavi?
>
> Thank you very much for your time,
>
> Claus
>
>
> --
> Claus Denk
> Vicerrectorado de Investigación
> Tel. 9544-88123
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>