You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Jay Verrone <JV...@odysseyauto.com> on 2011/12/22 15:39:18 UTC

AWS - guidance on preferred Operating System

I installed OpenMeetings on an AWS Small Instance we were running into some small issues.... possibly related to memory.
I will be installing a new version of OpenMeetings on a new AWS Instance and I'm looking for some guidance on the best or most preferred server setup.
I was also wondering if there is a preferred Open Meeting Build - or is the nightly build fine to start with.

Q:  - Could anyone recommend the preferred Operation System and release version

-          Debian

-          CentOS

-          Ubuntu

As well as ....

-          RED5

-          Open Office (all packages )

-          Libjpeg

-          libgif-devel

-          swftools

-          Imagemagick

-          FFMPEG

-          SoX


Also, I wanted to thank everyone for their contributions... especially Sebastian.

Re: AWS - guidance on preferred Operating System

Posted by Alexei Fedotov <al...@gmail.com>.
Small instances are good for small conferences
22.12.2011 18:39 пользователь "Jay Verrone" <JV...@odysseyauto.com>
написал:

> I installed OpenMeetings on an AWS Small Instance we were running into
> some small issues.... possibly related to memory.
> I will be installing a new version of OpenMeetings on a new AWS Instance
> and I'm looking for some guidance on the best or most preferred server
> setup.
> I was also wondering if there is a preferred Open Meeting Build - or is
> the nightly build fine to start with.
>
> Q:  - Could anyone recommend the preferred Operation System and release
> version
>
> -          Debian
>
> -          CentOS
>
> -          Ubuntu
>
> As well as ....
>
> -          RED5
>
> -          Open Office (all packages )
>
> -          Libjpeg
>
> -          libgif-devel
>
> -          swftools
>
> -          Imagemagick
>
> -          FFMPEG
>
> -          SoX
>
>
> Also, I wanted to thank everyone for their contributions... especially
> Sebastian.
>