Definitely a valid point up for discussion in my view, or even a quick rundown of all the common, node specific tooling, and where we should have the couple of 'yays' with a lot of 'nays' for the rest so the objective doesn't balloon.
I just don't want some to get hung up on Linux infrastructure. With rare exception, its out-of-scope. - bjs -- Sent from my Moto G7 Power, apologies for any brevity as well as the satanic versus of autocorrect Bryan J Smith - http://linkedin.com/in/bjsmith On Tue, Mar 10, 2020, 12:43 Fabian Thorns <[email protected]> wrote: > Hi Jeroen, > > On Tue, Mar 10, 2020 at 4:09 PM Jeroen Baten <[email protected]> wrote: > > Fair point. So, they should do LPI essentials first to be able to setup >> a Linux server with node.js? >> > > For a lab environment, it doesn't even have to be an entire server, it > could be as easy as typing 'node index.js'. We should consider adding the > 'node' command to the objectives, though. > > Fabian > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
