|
Aaron, (or anyone else)
Can you (or anyone else) tell me then how my system is already set to use
the old version vs. the new version? It must be something in the current
path.
Somewhere the system has to be being told "use this version". I want to
tell it to use the new version. This should be something simple to do I
would hope without making a shell script.
I see in /usr/bin the node command (v0.12.13) as well as many others (ls,
curl, jar, etc) Can I replace any files in there to make it use the new
version instead of writing a script?
Sorry to be a pest, but this will be asked MANY times in the future, I'm
sure of it. :)
When I use
echo $PATH
I get:
/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
When I use
export PATH=/QOpenSys/QIBM/ProdData/OPS/Node4/bin:$PATH
And then node -v, it does claim to be using the new version. But... I want
to set it to use it system wide, not just for my particular session.
Am I asking the wrong question? :) I apologize if I am... but I would
hope this would be something simple, something documented by IBM (or the
OSS group).
IBM released Node4, I would hope there were some documentation on how to
set your system to use it besides needed to create a shell script. When
they release the next version, the path would be the same to use the new
version, or to be able to go back to the old version.
Brad
On Wed, Jul 6, 2016 at 4:28 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
I use shell scripts to set the environment before starting my app. Forthe
example:
---start.sh---
export PATH=/QOpenSys/QIBM/ProdData/OPS/Node4/bin:$PATH
PORT=80 node app.js
And then put it in a SBMJOB..
SBMJOB JOB(QSH CMD('/path/to/start.sh'))
Aaron Bartell
litmis.com - Services for open source on IBM i
On Wed, Jul 6, 2016 at 4:23 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:
Yep, it shows v0.12.13. I know node4 is installed. I also know how tothe
check the version.
So, again I ask, how do I tell my applications (or my system if that's
right terminology) to use the new version?wrote:
On Wed, Jul 6, 2016 at 3:43 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:
Before you start your app you can run:
node -v
From within your app you could try this:
http://bit.ly/determine-nodejs-version
Aaron Bartell
litmis.com - Services for open source on IBM i
On Wed, Jul 6, 2016 at 3:38 PM, Bradley Stone <bvstone@xxxxxxxxx>
I'm
Any other changes to source needed besides that? How do I know if
using the new or old Node version with my application? (not just
hasDB2aaronbartell@xxxxxxxxx>
adapter).
On Wed, Jul 6, 2016 at 3:31 PM, Aaron Bartell <
wrote:
That depends what you mean by "convert". Node4 uses ES6 which
abe
number
of new features. With that said, the primary thing you need to
require('/QOpenSys/QIBM/ProdData/Node/os400/db2i/lib/db2')aware
of
is the changed path of the DB2 adapter. Going off of memory...
Node v0.12.x
var db =
listrequire('/QOpenSys/QIBM/ProdData/OPS/Node4/os400/db2i/lib/db2')
Node v4.x
var db =
Aaron Bartell
litmis.com - Services for open source on IBM i
On Wed, Jul 6, 2016 at 3:24 PM, Bradley Stone <bvstone@xxxxxxxxx
wrote:version
Just looking through my system I see I have Node4 installed.
Is there a "simple" way to convert my apps done with the old
to
use
the new version?
--
This is the IBMi Open Source Roundtable (OpenSource) mailing
----------To post a message email: OpenSource@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.