You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/05/14 06:01:20 UTC

[jira] [Resolved] (OPENMEETINGS-614) Docomentation

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved OPENMEETINGS-614.
-------------------------------------------

    Resolution: Won't Fix
      Assignee: Maxim Solodovnik

The documentation mentioned here was provided by OM user, please contact him directly to get it fixed

We have no availability to add required changes :(

> Docomentation
> -------------
>
>                 Key: OPENMEETINGS-614
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-614
>             Project: Openmeetings
>          Issue Type: Task
>    Affects Versions: 2.1.0 Apache Release
>         Environment: unix
>            Reporter: Thomas Osterried
>            Assignee: Maxim Solodovnik
>            Priority: Trivial
>              Labels: documentation
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Document: "Installing OM2.x On Debian64 Wheezy - Headless.pdf"
> 1. java: latest version is jdk1.6.0_43. I think it's important to advice the newest version, due to the many issues java has.
> 2. swftools are available in a newer version
> 3. ffmpeg also
> 4. password = "password" for the database connection is not a wise recommendation. At least you should warn the reader.
> 5. cut+paste of  /etc/init.d/red5 did not work correctly (I used macosx "preview" pdf reader). Not only every line startet at col 1. Sometimes, there was no linefeed, and sometimes lins got out of order
> 6. page 25:
>     "Make backup copy
> mv /usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml \ /usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml-ori"
>   You meant "cp", not "mv".
> 7. security considerations:
>    chown -R nobody /usr/lib/red5 (page 23).I'd _really_ feel better if static data is owned by root (and != uid of the red5 process) and only certain directories have the permissions for om and it's components to write. Being new to OM, I can't see, in which of the 71 directories data like uploaded docoments, paints, session recordings, etc.. are stored. Btw - they should better go to /var (which is the place for dynamic growing data).



--
This message was sent by Atlassian JIRA
(v6.2#6252)