From dfa13efe634ca8feb61689d3107b889c7acf4ee2 Mon Sep 17 00:00:00 2001 From: Dannon Baker Date: Mon, 6 May 2019 13:52:26 -0400 Subject: [PATCH] Update doc on NodeJS version compatibility (I updated proxy deps a while back, works with modern node now) --- .../special_topics/interactive_environments.rst | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/doc/source/admin/special_topics/interactive_environments.rst b/doc/source/admin/special_topics/interactive_environments.rst index f075f041295..f7e7fce324c 100644 --- a/doc/source/admin/special_topics/interactive_environments.rst +++ b/doc/source/admin/special_topics/interactive_environments.rst @@ -36,17 +36,13 @@ and `Ansible Galaxy `__. Setting up the Proxy ^^^^^^^^^^^^^^^^^^^^ -Currently the Galaxy proxy is a NodeJS+Sqlite3 proxy. +The Galaxy IE Proxy is a NodeJS+Sqlite3 application. The NodeJS that is +installed by default into the Galaxy Virtualenv is suitable for an execution +environment for the Galaxy IE Proxy. -- Node has recently upgraded, and our proxy is pinned to an old version of - sqlite3. As such you'll currently need to have an older version of Node - available (0.10.X - 0.11.X vintage). -- One can use `NVM `__ to install and manage multiple versions of Node. -- We're working on solutions in this space to provide a better deployment - mechanism here and fewer dependencies. -- Please note that if you have NodeJS installed under Ubuntu, it often - installs to ``/usr/bin/nodejs``, whereas ``npm`` expects it to be - ``/usr/bin/node``. You will need to create that symlink yourself. +- Note that if you have NodeJS installed under Ubuntu, it often installs to + ``/usr/bin/nodejs``, whereas ``npm`` expects it to be ``/usr/bin/node``. You + may need to create that symlink yourself. Once Node and npm are ready to go, you'll need to install the dependencies