Galaxy local for production (not development)

Question: Galaxy local for production (not development)

3.3 years ago by

vebaev • 130

vebaev • 130 wrote:

Is it obligatory to move to mySQL and others options for production, or I can work also as it is - https://wiki.galaxyproject.org/Admin/Config/Performance/ProductionServer

production galaxy • 660 views

ADD COMMENT • link •

modified 3.3 years ago by christophe.habib • 340 • written 3.3 years ago by vebaev • 130

It will be used by less than 5 users, mainly NGS analysis - bowtie, tophat, SAM, BAM analysis, visualizations, etc

ADD REPLY • link written 3.3 years ago by vebaev • 130

3.3 years ago by

Hotz, Hans-Rudolf • 1.8k

Switzerland

Hotz, Hans-Rudolf • 1.8k wrote:

Yes, it is highly recommended to switch to PostgreSQL for a production server (e.g in order to omit data-locks, when two or more users accessing galaxy at the same time).

WRT the other recommendations: it all depends on how many users, how much data, what kind of tools, etc your galaxy server is used for. But in general these are all very good suggestions to implement.

Regards, Hans-Rudolf

ADD COMMENT • link written 3.3 years ago by Hotz, Hans-Rudolf • 1.8k

3.3 years ago by

christophe.habib • 340

France

christophe.habib • 340 wrote:

Hi Ve379,

If you follow step by step what is written on the wiki, it should work with no problems. The page is really well documented. I have had many bugs with mysql database, so I recommend you PostgreSQL for your production instance.

Regards,

Christ

ADD COMMENT • link written 3.3 years ago by christophe.habib • 340

Please log in to add an answer.

Similar posts • Search »