Node: Installation and Upgrade

Node is installed using nvm and nodejs packages are install using npm.

Initial Installation

1.  Install nvm

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh | bash

2. Install node version 4

nvm install 4

Upgrade NVM and Node version

1. Upgrade nvm using

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash

creationix/nvm/v0.32.0/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10007  100 10007    0     0   5040      0  0:00:01  0:00:01 --:--:--  5038
=> nvm is already installed in /Users/Seet/.nvm, trying to update using git
=> 
=> Source string already in /Users/Seet/.bash_profile
=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="/Users/Seet/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

2. Upgrade to stable node js 5 version

nvm install 5

######################################################################## 100.0%
Computing checksum with shasum -a 256
Checksums matched!
Now using node v5.12.0 (npm v3.8.6)

3. Uninstall node js 4

nvm uninstall 4

4. Set nvm alias to avoid this error: "N/A: version "N/A" is not yet installed."

nvm alias default v5.12.0

5. Useful command for debugging

> nvm alias

default -> v5.12.0
node -> stable (-> v5.12.0) (default)
stable -> 5.12 (-> v5.12.0) (default)
iojs -> N/A (default)
lts/* -> lts/argon (-> N/A)
lts/argon -> v4.6.0 (-> N/A)

> nvm debug

nvm --version: v0.32.0
$SHELL: /bin/bash
$HOME: /Users/Nebitrams
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: v5.12.0
which node: $NVM_DIR/versions/node/v5.12.0/bin/node
which iojs:
which npm: $NVM_DIR/versions/node/v5.12.0/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v5.12.0
npm root -g: $NVM_DIR/versions/node/v5.12.0/lib/node_modules

Upgrade NPM

1. Upgrade nvm using

npm install -g npm@latest

Common Issue for Parse-server Upgrade

This is a common error during upgrade of parse-server.  After upgrade, the npm start may ends with error like this: "Cannot find module 'double-ended-queue'".

If you run npm list, you will see some missing modules such as the followings:

npm ERR! missing: double-ended-queue@^2.1.0-0, required by redis@2.8.0
npm ERR! missing: redis-commands@^1.2.0, required by redis@2.8.0
npm ERR! missing: redis-parser@^2.6.0, required by redis@2.8.0

 You can try to delete the package-lock.json and node_modules folder, following by re-install.

rm -rf package-lock.json node_modules/
npm i --no-optional
npm dedupe
npm up

Refer to https://github.com/npm/npm/issues/19393 for more information.

MongoDB : regular version upgrade

The local MongoDB instance was installed using brew.

Initial Installation

1. Install Xcode command-line toolsxcode-select --install
2. install home-brew

Upgrade locally installed mongodb

1. Upgrade brew by running

"brew update"

2. Upgrade mongodb by running

"brew upgrade mongodb"

==> Upgrading 1 outdated package, with result:
mongodb 3.2.10
==> Upgrading mongodb
==> Installing dependencies for mongodb: openssl
==> Installing mongodb dependency: openssl
==> Downloading https://homebrew.bintray.com/bottles/openssl-1.0.2j.el_capitan.b
######################################################################## 100.0%
==> Pouring openssl-1.0.2j.el_capitan.bottle.tar.gz
==> Using the sandbox
==> Caveats
A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
  /usr/local/etc/openssl/certs

and run
  /usr/local/opt/openssl/bin/c_rehash

This formula is keg-only, which means it was not symlinked into /usr/local.

Apple has deprecated use of OpenSSL in favor of its own TLS and crypto libraries

Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:

    LDFLAGS:  -L/usr/local/opt/openssl/lib
    CPPFLAGS: -I/usr/local/opt/openssl/include

==> Summary
🍺  /usr/local/Cellar/openssl/1.0.2j: 1,695 files, 12M
==> Installing mongodb
==> Downloading https://homebrew.bintray.com/bottles/mongodb-3.2.10.el_capitan.b
######################################################################## 100.0%
==> Pouring mongodb-3.2.10.el_capitan.bottle.tar.gz
==> Caveats
To have launchd start mongodb now and restart at login:
  brew services start mongodb
Or, if you don't want/need a background service you can just run:
  mongod --config /usr/local/etc/mongod.conf
==> Summary
🍺  /usr/local/Cellar/mongodb/3.2.10: 18 files, 245.2M

Upgrade local mongodb from 3.4.18 to 3.6

This is to document the process of upgrading from currently installed 3.4.18 to 3.6.11.  Using brew upgrade doesn't work for me and I used brew install mongodb@3.6.  However, the drawback is I only managed to install 3.6.8 (not sure why 3.6.11 is not available).  Refer to this link for more information.  Upgrade to specific version of MongoDB

1. Prepare the data by running this using mongo shell.

db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )

2. Upgrade brew by running will result in installing the latest which is 4.0 as of May 2019

"brew upgrade mongodb"

3. Install a specific version by using

"brew install mongodb@3.6"

4. Update the link using

"brew unlink mongodb@3.4"

"brew link --force mongodb@3.6"

5. Open a new shell and check the default MongoDB version

mongod --version
db version v3.6.8
git version: <snipped>
OpenSSL version: OpenSSL 1.0.2r  26 Feb 2019
allocator: system
modules: none
build environment:
    distarch: x86_64
    target_arch: x86_64

5. If you see this error when you start up mongod.  Then you need to set.  Read error-while-upgrading-mongodb-from-3-2-to-3-6

IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details.

 6. If you need to switch back to mongodb version 3.4.  Use the brew link and unlink.  After that, you can switch back to 3.6 by unlink and link again.

"brew unlink mongodb@3.6"
"brew link --force mongodb@3.4"

Upgrade mLab mongodb version

General steps for upgrade:

1. Check the mLab upgrade guide.
2. Test the application in staging environment

Once all test is completed, upgrade the mLab using Tool -> version.

ParseServer: managing mLab test environment

Prerequisites

1. You have completed the setup of a production mLab database.
2. You have mongoLab client installed in your computer so that you can run these
1. mongodump
2. mongorestore

Objective

Copy from mLab production database to another mLab staging database.

mLab cloud backup vs local backup

The copy of production database to test database is achieved using backup and restore mechanism. mLab provides cloud based backup and restore functionality using the web based admin page.  However, each backup cost 50 cents.  Alternatively, you can achieve this free of charge by installing your own mongoLab client in your computer and perform backup to your local computer and then restore to another test database in mLab.

Copy mLab database from production to staging using local backup

You will first need to run a mongodump to backup your mLab production database to your local PC.  After that you run mongorestore to restore your local PC database backup to another mLab staging database.  

MongoDB provides two mechanisms for importing and exporting data. One way is via the mongoimport and mongoexport utilities. These allow you to import and export JSON and CSV representations of your data. The other way is with mongorestore and mongodump utilities which deal with binary dumps.

The commands to dump, delete all tables/data and restore are as follows:

1. mongodump -h <production-hostname> -d <production-database-name> -u <user> -p <password> -o <output directory>
2. mongo <staging-hostname>/<staging-database-name> -u <user> -p <password> --eval "db.dropDatabase();"
3. mongorestore -h <staging-hostname> -d <staging-database-name> -u <user> -p <password> <input db directory>

ParseServer: managing Heroku test environment

Prerequisites

You have completed the setup of app in both

1. local, i.e your own computer
2. hosted on heroku, i.e this is the app that you deployed using "git push heroku master"

Refer to this heroku page for the details on creating staging, integration environments for the same application.  All the command below need to be ran in the heroku directory.  Heroku toolbelt is installed and you are logon using your heroku credential.

Objective

Setup a staging Heroku application.  A staging application is useful for testing new features in a production lookalike environment before releasing to production.

Checking your existing Git Remote

All applications on heroku are created with the default git remote as "heroku".  You can check the git remote using this command:

git remote -v

The command returns remotes as follows.  The heroku remote is the app that I deployed to the heroku.  The origin remote came from the git clone command when I clone from the parse-server-example git.

> origin    https://github.com/ParsePlatform/parse-server-example.git (fetch)
> origin    https://github.com/ParsePlatform/parse-server-example.git (push)
> heroku    https://git.heroku.com/elochallenge.git (fetch)
> heroku    https://git.heroku.com/elochallenge.git (push) 

In this setup, I want to create elochallengestaging app from elochallenge app.  After the setup, I will have these 2 applications in Heroku.

1. elochallenge
2. elochallengestaging

Creating a Staging Environment

Run the following command to create a staging environment.

heroku fork --from elochallenge --to elochallengestaging

Add a new git remote using this command.

git remote add elochallengestaging https://git.heroku.com/elochallengestaging.git

Run this again to confirm that remote is created successfully.

 git remote -v

Setting Configuration Variables

After the new environment is created.  You will need to set the configuration variables.  Run these command line.

1. heroku config:set DATABASE_URI=xxx --remote  elochallengestaging
2. heroku config:set MASTER_KEY=xxx --remote  elochallengestaging
3. heroku config:set SERVER_URL=xxx --remote  elochallengestaging

You can also update the configuration variable using Heroku web admin page.

Publish Changes to Staging and Production Environment

When you are ready to test your code in staging, run the following command to push to staging.

git push elochallengestaging master

After testing in the staging environment is completed, you may push your changes to production.

git push heroku master

Pulling latest code from ParseServer github

The git remote that you checked out the source code via "git clone" will be updated with new releases.  Once you are ready to get the latest release, run one of the git pull command below from your local git folder.

• git pull https://github.com/ParsePlatform/parse-server-example.git
• git pull origin

If you see conflicts, check for the filename with conflict and use editor to resolve the merge conflict manually.  For example, this is a conflict in package.json

remote: Counting objects: 11, done.
remote: Total 11 (delta 6), reused 6 (delta 6), pack-reused 5Unpacking objects: 100% (11/11), done.
From https://github.com/ParsePlatform/parse-server-example   5eea333..084fa07  master     -> origin/master * [new branch]      parse-server-version -> origin/parse-server-versionAuto-merging package.json
CONFLICT (content): Merge conflict in package.json
Auto-merging index.jsAutomatic merge failed; fix conflicts and then commit the result.

After resolving conflicts, run the npm to get the latest.

• npm outdated : to list the outdated modules. Sample output as follows.

Package       Current  Wanted  Latest  Locationexpress        4.13.4  4.13.4  4.14.0  express parse-server   2.2.10  2.2.14  2.2.14  parse-server

• npm update : to get the latest modules to local computer
• npm list : to list all the modules installed locally

Once you are ready, do a git add, git commit and deploy it to the staging environment by using git push command.

• git push elochallengestaging master

Setting Git Defaults

You can set the git push defaults to the staging environment.  Run the following command to list all the git config.

git config -l

Run this to setup the push default to elochallengestaging.

git config push.default elochallengestaging

After setting up the default, you can push to the elochallengestaging by running this command.

git push