Re: [IBMiOSS] chroot or not for node?

so, why not just create a directory for node8 and install it there with

yum, then have all your applications point to that directory?

At the end of the day a chroot gives you boundaries. Once inside a chroot
an application/developer can't hose the base of PASE by doing something
silly (installing rpms that ruin another developer's environment).

I like to think of chroot containers as being similar to how I use
VirtualBox for testing Linux Distros. I can easily spin one up to try
something. I can keep it as long as I want. I can delete it and start
over if I screwed it up.

Another big advantage is you can script the creation of developer and
production chroot containers, and that script can be stored in Git so your
environments are change managed.



Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces


On Mon, Mar 19, 2018 at 12:19 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Ok, in going through this chroot stuff (because it's not working) led me to
this..

The docs say you can use yum to install like this:

yum --installroot=<path too chroot> install <package list>

so, why not just create a directory for node8 and install it there with
yum, then have all your applications point to that directory?

What the need for chroot in this case? It seems copying over the entire
environment for each chroot when all you want is different versions of node
in different locations would be overkill.




Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #5 <https://www.bvstools.com/mailtool.html>: Easy setup!
No confusing or obscure setup instructions, directory entries, SMTP users,
aliases or host tables. All you need is TCPIP, a connection to the internet
and you're done!
--
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: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.