Hi Armand,

Certainly vagrant is not needed, but the build environment for the project is all geared around Ansible for consistency.

If you bring up an Ubuntu images on vmware you can run Ansible against it to configure it - you just need to provide an inventory file that references your own instances.  You can also customise for your own environment and have an instance for the backend, and another for the front end etc by changing the roles in the inventory file in Ansible.  That is effectively what we will do in the EC2 machines next week as well.

We don’t prepare prebuilt boxes, but you are quite correct that it could be done - they will have a pretty limited audience though.  If someone wanted to contribute by preparing some boxes on a daily cron to always have the latest released code, that would be a welcome addition.

Cheers,
Tim

On 29 Apr 2015, at 09:29, Armand Turpel <armand.turpel@gmail.com> wrote:

> Hi,
>
> It would be useful to have a detailed instruction on how to install the ala-portal on a existing linux instance without vagrant and ansible. We have linux instances which run on vmware hosts. And of course on virtualbox windows host.
> For testings I could also be useful to distribute linux instances with pre-installed ala-portal. That could simplify things for a first test. As seen on the upcoming Paris workshop Amazon EC2 instances will be provided. I guess such instances can be installed on a virtualbox host?
>
> Best wishes,
> Armand
>
> _____________________________
> Service Information sur le Patrimoine naturel
> Musée national d’histoire naturelle
> 25, rue Munster
> L-2160 Luxembourg

> _______________________________________________
> Ala-portal mailing list
> Ala-portal@lists.gbif.org
> http://lists.gbif.org/mailman/listinfo/ala-portal