DOCSLIB.ORG

Complete Node.Js Secrets & Tips for Professionals

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Complete Node.Js Secrets & Tips for Professionals Node.js CompleteComplete Tips & Secrets for Professionals Node.js Tips & Secrets for Professionals 200+ pages of professional hints and tricks Disclaimer This is an unocial free book created for educational purposes and is GoalKicker.com not aliated with ocial Node.js group(s) or company(s). Free Programming Books All trademarks and registered trademarks are the property of their respective owners Contents About ................................................................................................................................................................................... 1 Chapter 1: Getting started with Node.js ............................................................................................................ 2 Section 1.1: Hello World HTTP server ........................................................................................................................... 3 Section 1.2: Hello World command line ....................................................................................................................... 4 Section 1.3: Hello World with Express .......................................................................................................................... 5 Section 1.4: Installing and Running Node.js ................................................................................................................. 6 Section 1.5: Debugging Your NodeJS Application ...................................................................................................... 6 Section 1.6: Hello World basic routing ......................................................................................................................... 7 Section 1.7: Hello World in the REPL ............................................................................................................................ 8 Section 1.8: Deploying your application online ........................................................................................................... 8 Section 1.9: Core modules ............................................................................................................................................. 8 Section 1.10: TLS Socket: server and client ................................................................................................................ 13 Section 1.11: How to get a basic HTTPS web server up and running! ..................................................................... 15 Chapter 2: npm ............................................................................................................................................................ 17 Section 2.1: Installing packages ................................................................................................................................. 19 Section 2.2: Uninstalling packages ............................................................................................................................ 22 Section 2.3: Setting up a package configuration ..................................................................................................... 23 Section 2.4: Running scripts ....................................................................................................................................... 23 Section 2.5: Basic semantic versioning ..................................................................................................................... 24 Section 2.6: Publishing a package ............................................................................................................................. 25 Section 2.7: Removing extraneous packages .......................................................................................................... 25 Section 2.8: Listing currently installed packages ..................................................................................................... 25 Section 2.9: Updating npm and packages ............................................................................................................... 26 Section 2.10: Scopes and repositories ....................................................................................................................... 26 Section 2.11: Linking projects for faster debugging and development .................................................................. 26 Section 2.12: Locking modules to specific versions ................................................................................................. 27 Section 2.13: Setting up for globally installed packages ......................................................................................... 27 Chapter 3: Web Apps With Express .................................................................................................................... 28 Section 3.1: Getting Started ......................................................................................................................................... 28 Section 3.2: Basic routing ........................................................................................................................................... 29 Section 3.3: Modular express application ................................................................................................................. 30 Section 3.4: Using a Template Engine ....................................................................................................................... 31 Section 3.5: JSON API with ExpressJS ....................................................................................................................... 33 Section 3.6: Serving static files ................................................................................................................................... 33 Section 3.7: Adding Middleware ................................................................................................................................. 34 Section 3.8: Error Handling ......................................................................................................................................... 34 Section 3.9: Getting info from the request ................................................................................................................ 35 Section 3.10: Error handling in Express ...................................................................................................................... 36 Section 3.11: Hook: How to execute code before any req and after any res ........................................................ 36 Section 3.12: Setting cookies with cookie-parser ..................................................................................................... 36 Section 3.13: Custom middleware in Express ............................................................................................................ 37 Section 3.14: Named routes in Django-style ............................................................................................................. 37 Section 3.15: Hello World ............................................................................................................................................. 38 Section 3.16: Using middleware and the next callback ............................................................................................ 38 Section 3.17: Error handling ........................................................................................................................................ 40 Section 3.18: Handling POST Requests ...................................................................................................................... 41 Chapter 4: Filesystem I/O ...................................................................................................................................... 42 Section 4.1: Asynchronously Read from Files ........................................................................................................... 42 Section 4.2: Listing Directory Contents with readdir or readdirSync ..................................................................... 42 Section 4.3: Copying files by piping streams ............................................................................................................ 43 Section 4.4: Reading from a file synchronously ...................................................................................................... 44 Section 4.5: Check Permissions of a File or Directory ............................................................................................. 44 Section 4.6: Checking if a file or a directory exists .................................................................................................. 45 Section 4.7: Determining the line count of a text file ............................................................................................... 45 Section 4.8: Reading a file line by line ....................................................................................................................... 46 Section 4.9: Avoiding race conditions when creating or using an existing directory ........................................... 46 Section 4.10: Cloning a file using streams ................................................................................................................. 46 Section 4.11: Writing to a file using writeFile or writeFileSync ................................................................................. 47 Section 4.12: Changing contents
Load more

Recommended publications
  • Rekstrarhandbók
    Vorönn 2017 T-404-LOKA, Lokaverkefni Rekstrarhandbók Ingþór Birkir Árnason Jan Hinrik Hansen Logi Guðmann Þorgrímur Jónasarson Kennari: Hallgrímur Arnalds Leiðbeinandi: Sigurjón Ingi Garðarsson Prófdómari: Símon Óttar Vésteinsson 12. maí 2017 Efnisyfirlit 1 Framendi 3 1.1 Dependencies 3 1.2 Uppsetning 3 1.3 Keyrsla 3 1.4 ESLint 4 1.5 Stílar 5 1.5.1 BEM - Block Element Modifier 5 1.5.2 StyleLint 5 1.5.3 Gulp task 5 2 Bakendi 6 2.1 Dependencies 6 2.2 Uppsetning 6 2.3 Handhægar upplýsingar 8 2.3.1 Admin aðgangur 8 2.3.2 Postman 8 2.4 PHPUnit 8 2.5 Documentation 9 3 Forritunarreglur 9 3.1 Almennar reglur 9 3.2 VueJS 9 3.3 CSS 10 3.4 PHP - Laravel 11 2 1 Framendi Framendinn er skrifaður í Vue.js með vue-webpack-boilerplate (https://github.com/vuejs-templates/webpack) sem grunn. ​ ​ 1.1 Dependencies Til þess að geta keyrt framendann er nauðsynlegt að hafa node og node package manager (npm). Hægt er að sækja node.js ásamt npm á Node.js heimasíðunni (https://nodejs.org/en/). ​ ​ 1.2 Uppsetning 1.) Sækja git repository-ið. git clone https://github.com/toggi737/Lokaverkefni_vue.git 2.) Setja upp nauðsynleg dependencies í gegnum npm. npm install 3.) Búa til dev.env.js skrá sem að inniheldur stillingar fyrir þína vél. Nauðsynlegt er að búa til dev.env.js skrá undir config möppunni sem að inniheldur upplýsingar um þann API sem að þú vilt nota. Það er hægt að gera með því að keyra cp dev.env.js.example dev.env.js í config möppunni.
    [Show full text]
  • Learning React Functional Web Development with React and Redux
    Learning React Functional Web Development with React and Redux Alex Banks and Eve Porcello Beijing Boston Farnham Sebastopol Tokyo Learning React by Alex Banks and Eve Porcello Copyright © 2017 Alex Banks and Eve Porcello. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/insti‐ tutional sales department: 800-998-9938 or [email protected]. Editor: Allyson MacDonald Indexer: WordCo Indexing Services Production Editor: Melanie Yarbrough Interior Designer: David Futato Copyeditor: Colleen Toporek Cover Designer: Karen Montgomery Proofreader: Rachel Head Illustrator: Rebecca Demarest May 2017: First Edition Revision History for the First Edition 2017-04-26: First Release See http://oreilly.com/catalog/errata.csp?isbn=9781491954621 for release details. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Learning React, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.
    [Show full text]
  • React.Pdf Email: [email protected] Twitter: @Mark Volkmann Github: Mvolkmann Website
    Say “No” to Complexity! Mark Volkmann, Object Computing, Inc. http://ociweb.com/mark/MidwestJS/react.pdf Email: [email protected] Twitter: @mark_volkmann https://github.com/mvolkmann/react-examples GitHub: mvolkmann Website: http://ociweb.com/mark Copyright © 2015-2016 by Object Computing, Inc. (OCI) All rights reserved Intro. Meaning behind the talk title - 2 kinds of complexity other frameworks state management approaches: thunks, sagas, epics, effects, GraphQL, Relay, Falcor, ... Why are the slides so dense? Copyright © 2015-2016 by Object Computing, Inc. (OCI) React All rights reserved 2 What is OCI? Software development (on-site and off-site), consulting, and training Home of Grails, “An Open Source high-productivity framework for building fast and scalable web applications” Open Source Transformation Services helping clients move from commercial to open source software Industrial Internet of Things (IIoT) DevOps Copyright © 2015-2016 by Object Computing, Inc. (OCI) React All rights reserved 3 Overview ... Web app library from Facebook As of 8/6/16, React was reportedly used by Airbnb, Angie’s List, http://facebook.github.io/react/ Atlasssian, BBC, Capitol One, Clash of Focuses on view portion Clans, Codecademy, Coursera, Docker, Dropbox, Expedia, Facebook, Feedly, not full stack like other frameworks such as AngularJS and EmberJS Flipboard, HipChat, IMDb, Instagram, Intuit, Khan Academy, Lyft, New York use other libraries for non-view functionality Times, NFL, NHL, Netflix, Paypal, some are listed later Periscope, Reddit, Salesforce, Squarespace, Tesla Motors, Twitter, “One-way reactive data flow” Uber, Visa, WhatsApp, Wired, Wolfrum UI reacts to “state” changes Alpha, Wordpress, Yahoo, Zendesk, and many more. not two-way data binding like in AngularJS 1 Source: https://github.com/facebook/ what triggered a digest cycle? react/wiki/Sites-Using-React should I manually trigger it? easier to follow flow of data events -> state changes -> component rendering Copyright © 2015-2016 by Object Computing, Inc.
    [Show full text]
  • Air Quality Monitoring Toolkit: Assessing Second-Hand Smoke in Hospitality Venues
    Air Quality Monitoring Toolkit: Assessing Second-Hand Smoke in Hospitality Venues Authors: Dr Angela Jackson-Morris, Department of Tobacco Control, The International Union Against Tuberculosis and Lung Disease, Edinburgh, Scotland; Dr Sean Semple, Scottish Centre for Indoor Air, Respiratory Group, Division of Applied Health Sciences, University of Aberdeen, Aberdeen, Scotland; Ruaraidh Dobson, Scottish Centre for Indoor Air, Child Health, University of Aberdeen, Aberdeen, Scotland. About the International Union Against Tuberculosis and Lung Disease (The Union): For nearly 100 years, The Union has drawn from the best scientific evidence and the skills, expertise and reach of its staff, consultants and membership in order to advance solutions to the most pressing public health challenges affecting people living in poverty around the world. With nearly 17,000 members and subscribers from 156 countries, The Union has its headquarters in Paris and regional offices in Africa, the Asia Pacific, Europe, Latin America, North America and South-East Asia. The Union’s scientific departments focus on tuberculosis and HIV, lung health and non- communicable diseases, tobacco control and operational research. For more information on The Union’s tobacco control work please visit www.tobaccofreeunion.org or follow us on Twitter @TheUnion_TC. Contact: The International Union Against Tuberculosis and Lung Disease (The Union) Department of Tobacco Control 8 Randolph Crescent Edinburgh UK EH3 7TH T: 0131 240 0252 E: [email protected] About the University of Aberdeen: Founded in 1495, the University of Aberdeen is Scotland's third oldest and the UK's fifth oldest university, and is consistently ranked among the top 1 percent of the world's universities.
    [Show full text]
  • Npm Packages As Ingredients: a Recipe-Based Approach
    npm Packages as Ingredients: a Recipe-based Approach Kyriakos C. Chatzidimitriou, Michail D. Papamichail, Themistoklis Diamantopoulos, Napoleon-Christos Oikonomou, and Andreas L. Symeonidis Electrical and Computer Engineering Dept., Aristotle University of Thessaloniki, Thessaloniki, Greece fkyrcha, mpapamic, thdiaman, [email protected], [email protected] Keywords: Dependency Networks, Software Reuse, JavaScript, npm, node. Abstract: The sharing and growth of open source software packages in the npm JavaScript (JS) ecosystem has been exponential, not only in numbers but also in terms of interconnectivity, to the extend that often the size of de- pendencies has become more than the size of the written code. This reuse-oriented paradigm, often attributed to the lack of a standard library in node and/or in the micropackaging culture of the ecosystem, yields interest- ing insights on the way developers build their packages. In this work we view the dependency network of the npm ecosystem from a “culinary” perspective. We assume that dependencies are the ingredients in a recipe, which corresponds to the produced software package. We employ network analysis and information retrieval techniques in order to capture the dependencies that tend to co-occur in the development of npm packages and identify the communities that have been evolved as the main drivers for npm’s exponential growth. 1 INTRODUCTION Given that dependencies and reusability have be- come very important in today’s software develop- The popularity of JS is constantly increasing, and ment process, npm registry has become a “must” along is increasing the popularity of frameworks for place for developers to share packages, defining code building server (e.g.
    [Show full text]
  • Open Source on IBM I Webinar Series Day 2 ERWIN EARLEY ([email protected]), SR
    Open Source on IBM i Webinar Series Day 2 ERWIN EARLEY ([email protected]), SR. SOLUTIONS CONSULTANT, PERFORCE, NOVEMBER 2019 2 | COMMON Webinar Series: Open Source on IBM i | November 2019 zend.com Day 1 Review • Introduction to Open Source on IBM i • Why is Open Source on IBM i Important • Understanding the PASE environment as the enabler of Open Source on IBM i • Getting Familiar with the PASE environment 2 | Zend by Perforce © 2019 Perforce Software, Inc. zend.com 3 | COMMON Webinar Series: Open Source on IBM i | November 2019 zend.com Day 2 Agenda • Setting up OSS EcoSystem on IBM i – ACS version • Exploring Containers on IBM i • Managing Open Source on IBM i • Exploring Open Source Programming Languages ▪ Integration with Db2 and ILE • After-Hours Lab: Containers & Setting up Development Environment • After-Hours Lab: Open Source Programming Languages 3 | Zend by Perforce © 2019 Perforce Software, Inc. zend.com IBM Systems Technical University © 3 4 | COMMON Webinar Series: Open Source on IBM i | November 2019 zend.com Setting up OSS Ecosystem on IBM i – ACS Version 4 | Zend by Perforce © 2019 Perforce Software, Inc. zend.com 5 | COMMON Webinar Series: Open Source on IBM i | November 2019 zend.com The directory structure Before installing the Open Source ecosystem / dev home lib sbin tmp usr var Directory Contents bin Commands dev Device Files etc Configuration files home User Home Directories lib Libraries pkgs Package files / commands sbin Privileged commands tmp Temporary files usr Utilities & Applications var Variable files
    [Show full text]
  • Means Nested Providers from the Real Client. for Example P->[email protected] Means That P2 Is the P’S Provider and P Is the Real Client’S Provider
    real client = the client package that we executed the release’s test. -> means nested providers from the real client. For example p->[email protected] means that p2 is the p’s provider and p is the real client’s provider. --------------------------------------------------------------------- 1) [email protected] changed a key in its code, that did not introduce an error, but it became incompatible with babel-eslint. The escope is not a babel-eslint’s provider. This error was fixed by [email protected], when its providers claimed that it should be fixed in babel-eslint. ● Issue in babel-eslint ● Issue in escope ● Pull-request in babel-eslint ● Fixed by provider babel-eslint, which is the provider of the real client. ● Category: incompatible providers version. 2) the real client has grunt-jslint->jslint@>=0.3.4 as its providers. The [email protected] started to use ES6 and moved all of ES5’s code to another file. The [email protected] did a downgrade in the jslint’s version. Specifically, the grunt-jslint uses the array JSLINT.error, which was moved to another file. jslint is a provider of grunt-jslint, and grunt-jslint is a provider of real client. ● Downgrade of jslint ● [email protected] diff ● [email protected] changelog ● Fixed by provider as client grunt-jslint, which is the client of jslint. ● Category: Feature change. 3) the real client has the [email protected] as its provider. The babel-preset-es2015-rollup has the babel-preset-es2015 as its provider, that is introducing an error.
    [Show full text]
  • Investigating the Reproducbility of NPM Packages
    Investigating the Reproducbility of NPM packages Pronnoy Goswami Thesis submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Master of Science in Computer Engineering Haibo Zeng, Chair Na Meng Paul E. Plassmann May 6, 2020 Blacksburg, Virginia Keywords: Empirical, JavaScript, NPM packages, Reproducibility, Software Security, Software Engineering Copyright 2020, Pronnoy Goswami Investigating the Reproducbility of NPM packages Pronnoy Goswami (ABSTRACT) The meteoric increase in the popularity of JavaScript and a large developer community has led to the emergence of a large ecosystem of third-party packages available via the Node Package Manager (NPM) repository which contains over one million published packages and witnesses a billion daily downloads. Most of the developers download these pre-compiled published packages from the NPM repository instead of building these packages from the available source code. Unfortunately, recent articles have revealed repackaging attacks to the NPM packages. To achieve such attacks the attackers primarily follow three steps – (1) download the source code of a highly depended upon NPM package, (2) inject mali- cious code, and (3) then publish the modified packages as either misnamed package (i.e., typo-squatting attack) or as the official package on the NPM repository using compromised maintainer credentials. These attacks highlight the need to verify the reproducibility of NPM packages. Reproducible Build is a concept that allows the verification of build artifacts for pre-compiled packages by re-building the packages using the same build environment config- uration documented by the package maintainers. This motivates us to conduct an empirical study (1) to examine the reproducibility of NPM packages, (2) to assess the influence of any non-reproducible packages, and (3) to explore the reasons for non-reproducibility.
    [Show full text]
  • Building-Frontend-Pipeline Short
    Building a Frontend Pipeline Nathaniel T. Schutta @ntschutta Ah JavaScript! It used to be so simple right? 1,500 line main.js. Our apps aren’t like that anymore though are they? JavaScript is a first class citizen now. Modern applications are many thousands of lines of JavaScript. We incorporate many libraries and frameworks. https://mobile.twitter.com/joeerl/status/930774515512201216 NPM all the things. JavaScript itself is evolving. Browsers are still an issue… The struggle is real. What do we do about it? Why do we need a pipeline at all? Not your older sister’s web apps. No longer a few thousands lines of JavaScript and jQuery. Adhoc approach can’t keep up with the complexity of modern JS apps. Apply the level of discipline to the frontend that we use on the backend. Linters to ensure our code doesn’t fall prey to common errors. Unit tests to ensure our changes didn’t break anything. Bundlers to minimize asynchronous requests to our servers. Transpilers so we can leverage ES6 in older browsers. Task runers to help tie it all together. JavaScript usage has exploded. Number one language on GitHub? Yep. Not a new phenomena either. We cannot afford to treat JavaScript as a one off. The same engineering discipline we use on “server side” code must apply. Of course for many of us, JavaScript *is* our server side language too! More than a few options. Try and clear some of that up today. Linters. Certain mistakes can be caught automatically. Static code analysis. Find bad patterns. Check style adherence.
    [Show full text]
  • Server-Side Rendering of React Applications in Enterprise Portals
    Bachelor’s Thesis Czech Technical University in Prague Faculty of Electrical Engineering F3 Department of Computer Science Server-side rendering of React applications in enterprise portals Václav Jančařík Supervisor: Ing. Martin Ledvinka Field of study: Software Engineering and Technology May 2019 ii ZADÁNÍ BAKALÁŘSKÉ PRÁCE I. OSOBNÍ A STUDIJNÍ ÚDAJE Příjmení: Jančařík Jméno: Václav Osobní číslo: 466301 Fakulta/ústav: Fakulta elektrotechnická Zadávající katedra/ústav: Katedra počítačů Studijní program: Softwarové inženýrství a technologie II. ÚDAJE K BAKALÁŘSKÉ PRÁCI Název bakalářské práce: Vykreslování React aplikací na straně serveru v enterprise portálech Název bakalářské práce anglicky: Server-side rendering of React applications in enterprise portals Pokyny pro vypracování: 1. Analyze the current state of the art in the field of server-side rendering of React applications and running React applications in portal solutions. 2. Design fundamental principles of integration of server-side rendering of React applications in the context of portal environments. 3. Based on your design, implement a server-side rendering solution for React applications embedded in enterprise portals. 4. Demonstrate the correctness of your solution by comparing client- side and server-side rendering output of an example application. 5. Compare the performance of your server-side rendering solution with standard client-side rendering. Seznam doporučené literatury: [1] K. Konshin, Next.js Quick Start Guide: Server-side rendering done right, Packt Publishing, 2018 [2] R. Sezov, Liferay in Action: The Official Guide to Liferay Portal Development, Manning Publications, 2011 [3] R. Wieruch, The Road to learn React: Your journey to master plain yet pragmatic React.js, 2018 Jméno a pracoviště vedoucí(ho) bakalářské práce: Ing.
    [Show full text]
  • To Complexity!
    Say “No” to Complexity! Mark Volkmann, Object Computing, Inc. Email: [email protected] Twitter: @mark_volkmann GitHub: mvolkmann Website: http://ociweb.com/mark https://github.com/mvolkmann/react-examples Copyright © 2015-2016 by Object Computing, Inc. (OCI) All rights reserved What is OCI? New home of Grails, “An Open Source high-productivity framework for building fast and scalable web applications” Open Source Transformation Services, IIoT, DevOps offsite development, consulting, training handouts available (includes Grails sticker) Copyright © 2015-2016 by Object Computing, Inc. (OCI) React All rights reserved 2 Overview ... Web app library from Facebook As of 1/2/16, React was reportedly used by Airbnb, Atlasssian, Capitol http://facebook.github.io/react/ One, Codecademy, Coursera, Dropbox, Focuses on view portion Expedia, Facebook, Firefox, Flipboard, HipChat, IMDb, Instagram, not full stack like other frameworks such as AngularJS and EmberJS Intuit, Khan Academy, NHL, Netflix, use other libraries for non-view functionality Paypal, Reddit, Salesforce, Squarespace, Tesla Motors, New York Times, Twitter, some are listed later Uber, WhatsApp, Wired, Wordpress, “One-way reactive data flow” Yahoo, Zendesk, and many more. Source: https://github.com/facebook/ UI reacts to “state” changes react/wiki/Sites-Using-React not two-way data binding like in AngularJS 1 Facebook uses React more than what triggered a digest cycle? Google uses Angular. should I manually trigger it? easier to follow flow of data from events to state changes to component rendering Copyright © 2015-2016 by Object Computing, Inc. (OCI) React All rights reserved 3 ... Overview Can use in existing web apps that use other frameworks start at leaf nodes of UI and gradually work up, replacing existing UI with React components Defines components that are composable whole app can be one component that is built on others Components get data to render from “state” and/or “props” Can render in browser, on server, or both ex.
    [Show full text]
  • Adapt Authoring Tool: Installation
    Adapt Authoring Tool: Installation UGA Training Capstone Team April 21, 2019 1 Contents 1 Installing Prerequisites 3 1.1 Installing Git . 3 1.1.1 Debian Based Install . 3 1.1.2 RPM Based Install . 3 1.2 NodeJS . 4 1.2.1 Debian Based Install . 4 1.2.2 RPM Based Install . 4 1.3 Grunt . 5 1.3.1 Update NPM . 5 1.3.2 Install Grunt . 5 1.4 MongoDB Community Edition . 6 1.4.1 Debian Based Install . 6 1.4.2 RPM Based Install . 6 1.5 FFmpeg . 7 1.5.1 Debian Based Install . 7 1.5.2 RPM Based Install . 7 2 Installing The Authoring Tool 8 2.1 Clone Adapt Authoring . 8 2.2 Install required NPM packages . 8 2.3 Install Script . 9 2.4 PM2: Process Manager . 11 2.4.1 Installing PM2 . 11 2.4.2 Starting The Server . 11 2 1 Installing Prerequisites The authoring tool and framework require other software to operate. This section will provide the directions on what to install. Instructions have been provided for installation on a Debian or RPM based server. Other instruc- tions are provided at each software packages website. Administrative or Sudo access is required to complete the installation. 1.1 Installing Git Git is a tool for managing source code, and makes it easier to download and update the software. Git may already be installed on the server to which you are installing the authoring tool, to check from command line: $ git --version. 1.1.1 Debian Based Install From the command line: $ sudo apt install git-all 1.1.2 RPM Based Install From the command line: $ sudo dnf install git-all 3 1.2 NodeJS NodeJS is an open source, cross-platform JavaScript run-time enviroment that executes JavaScript code outside of a browser.
    [Show full text]