[ensembl-dev] Combined Ensembl database installation for 37 and 38

[Steve Trevanion]

Hi,

We would recommend having two distinct MySQL servers for the GRCh38 and 
GRCh37 databases. This would be particularly significant for species 
other than human where the database name is not sufficient to identify 
the data it contains - for example the data in mus_musculus_core_84_38 
on ensembldb.ensembl.org:5306 is different to that in 
mus_musculus_core_84_38 on ensembldb.ensembl.org:3337

If you are interested in setting up two webservers I suggest having two 
separate checkouts of the code. You can run two servers on the same host 
as long as they use different ports. We routinely run multiple servers 
on the same hardware in this manner.

Regards,

Steve

On 23/06/16 17:41, Genomeo Dev wrote:
> Hi guys,
>
> Any ideas on the question below please?
>
> Thanks.
>
> G.
>
> On Wednesday, 22 June 2016, Genomeo Dev <genomeodev at gmail.com 
> <mailto:genomeodev at gmail.com>> wrote:
>
>     Dear Ensembl Dev team,
>
>     I am interested in installing the Ensembl database with the the
>     latest releases for GRCh37 and GRCh38. I have found the following
>     documentation for each genome build:
>
>     37
>     http://grch37.ensembl.org/info/docs/webcode/mirror/index.html
>
>     38
>     http://asia.ensembl.org/info/docs/webcode/mirror/index.html
>
>     My questions:
>
>     1. Do I have to install two separate instances of the ensembl
>     database for each build?
>
>     2. If yes, are there common parts of the two installations that
>     should only be done once?
>
>     3. If previous questions are irrelevant, what is the best format
>     for installing 37 and 38 together?
>
>     Thanks,
>
>     -- 
>     G.
>
>
>
> -- 
> G.
>
>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20160624/59987ef3/attachment.html>