openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Ghenov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENMEETINGS-576) Task from GSoC 2012
Date Mon, 18 Mar 2013 13:22:15 GMT

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

Alexey Ghenov updated OPENMEETINGS-576:
---------------------------------------

    Attachment: build.properties
                build.xml

Hello! I inserted webserver setup and configuration into build.xml. You need use "ant prepare-yaws
(opt -Dport=port_you_want_to_listen -Dadress=adress_you_wat_to_listen)" to deploy the yaws
webserver and configure openmeetings. Now yaws ready to work, /dist/yaws-1.95/bin/yaws. 

Tested envoiment - Debian unstable.

Yaws dependicies:
You need have Erlang installed.
And you need this lib libpam0g-dev.
                
> Task from GSoC 2012
> -------------------
>
>                 Key: OPENMEETINGS-576
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-576
>             Project: Openmeetings
>          Issue Type: New Feature
>         Environment: Unix
>            Reporter: Alexey Ghenov
>            Priority: Minor
>              Labels: gsoc2012, newbie
>         Attachments: build.properties, build.xml
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> - proper traffic tunnelling (images and screensharing now use 5080 port, SIP applet likely
uses different ports as well, while anything should be happy with 80 port); 
> - performance: getting rid of Apache httpd to improve openmeetings hosting performance
(Apache eats tons os megabytes - proper jetty configuration can be done as a part of tunelling
task);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message