Creating your own self-hosted PARSE server

As you might be aware, PARSE service is shutting down beginning of 2017. This was a really great solution to quickly spin up the infrastructure needed to build an app. I still have some of my apps relying on that infrastructure and I think it's time to make the move to my own self-hosted PARSE server (for local Development). Here you will find a quick guide through the initial configuration required to have your PARSE server up and running in no time.

PARSE is actually really easy to set up. You just need a NoSQL DB (MongoDB in this case) and then get the latest source code from GitHub to create your own PARSE self-hosted instance. My sandbox is a Windows 2012 R2 and I will guide you through the required steps in there.

The prerequisites are as follows:

• Node 4.3
• MongoDB version 2.6.x or 3.0.x
• Python 2.x (For Windows users, 2.7.1 is the required version)

Installing MongoDB.

First you'll need MongoDB. Download the latest version of MongoDB from here. In my case I installed version 3.2.6 for Windows Server 2008 R2 and later with SSL support.

Install the complete version and once finished, go to MongoDB folder and run mongod.exe command:

	C:\Program Files\MongoDB\Server\3.2\bin>mongod.exe
	2016-05-21T11:44:58.239+0100 I CONTROL [initandlisten] MongoDB starting : pid=396 port=27017 dbpath=C:\data\db\ 64-bit host=MYWIN2012
	2016-05-21T11:44:58.241+0100 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
	2016-05-21T11:44:58.243+0100 I CONTROL [initandlisten] db version v3.2.6
	2016-05-21T11:44:58.244+0100 I CONTROL [initandlisten] git version: 05552b562c7a0b3143a729aaa0838e558dc49b25
	2016-05-21T11:44:58.245+0100 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015
	2016-05-21T11:44:58.247+0100 I CONTROL [initandlisten] allocator: tcmalloc
	2016-05-21T11:44:58.248+0100 I CONTROL [initandlisten] modules: none
	2016-05-21T11:44:58.249+0100 I CONTROL [initandlisten] build environment:
	2016-05-21T11:44:58.250+0100 I CONTROL [initandlisten] distmod: 2008plus-ssl
	2016-05-21T11:44:58.252+0100 I CONTROL [initandlisten] distarch: x86_64
	2016-05-21T11:44:58.253+0100 I CONTROL [initandlisten] target_arch: x86_64
	2016-05-21T11:44:58.254+0100 I CONTROL [initandlisten] options: {}
	2016-05-21T11:44:58.257+0100 I STORAGE [initandlisten] exception in initAndListen: 29 Data directory C:\data\db\ not found., terminating
	2016-05-21T11:44:58.259+0100 I CONTROL [initandlisten] dbexit: rc: 100
	C:\Program Files\MongoDB\Server\3.2\bin>mongod.exe
	2016-05-21T11:47:53.589+0100 I CONTROL [initandlisten] MongoDB starting : pid=4376 port=27017 dbpath=C:\data\db\ 64-bit host=MYWIN2012
	2016-05-21T11:47:53.591+0100 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
	2016-05-21T11:47:53.594+0100 I CONTROL [initandlisten] db version v3.2.6
	2016-05-21T11:47:53.596+0100 I CONTROL [initandlisten] git version: 05552b562c7a0b3143a729aaa0838e558dc49b25
	2016-05-21T11:47:53.598+0100 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015
	2016-05-21T11:47:53.600+0100 I CONTROL [initandlisten] allocator: tcmalloc
	2016-05-21T11:47:53.604+0100 I CONTROL [initandlisten] modules: none
	2016-05-21T11:47:53.605+0100 I CONTROL [initandlisten] build environment:
	2016-05-21T11:47:53.607+0100 I CONTROL [initandlisten] distmod: 2008plus-ssl
	2016-05-21T11:47:53.610+0100 I CONTROL [initandlisten] distarch: x86_64
	2016-05-21T11:47:53.612+0100 I CONTROL [initandlisten] target_arch: x86_64
	2016-05-21T11:47:53.614+0100 I CONTROL [initandlisten] options: {}
	2016-05-21T11:47:53.616+0100 I STORAGE [initandlisten] wiredtiger_open config:create,cache_size=1G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
	2016-05-21T11:47:54.810+0100 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker
	2016-05-21T11:47:54.811+0100 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'C:/data/db/diagnostic.data'
	2016-05-21T11:47:55.093+0100 I NETWORK [initandlisten] waiting for connectionson port 27017

view raw mongo hosted with ❤ by GitHub

Notice that I had to run the command twice as the folder that MondoDB needs was not there: C:\data\db. I created the folder manually and then ran again the executable. Now MongoDB is up and running awaiting for connections on port 27017.

Installing Node.js.
Next step is to download and install Node.js. You can get the latest version here. I will install version 4.4.4 LTS which is the recommended for most users. Download the installer and continue clicking next until it is completely installed on your machine.

Installing Python.
The required version for Windows is 2.7.1. In my case I will install 2.7.11 as it's the recommended version from Python. You can get the latest installer from here. Once the setup is completed you will have to reboot your machine to make sure the configuration is updated.

Downloading PARSE server example.
Head to PARSE server source code on GitHub and download the PARSE server example from here. Unzip the zip file under C:\Parse for example. Once everything is in place, open node.js command prompt with admin rights and run the command npm install under C:\Parse folder:

	Your environment has been set up for using Node.js 4.4.4 (x64) and npm.
	C:\Parse>npm install
	> kerberos@0.0.21 install C:\Parse\node_modules\kerberos
	> (node-gyp rebuild) || (exit 0)
	/
	C:\Parse\node_modules\kerberos>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild )
	Building the projects in this solution one at a time. To enable parallel build,please add the "/m" switch.
	MSBUILD : error MSB4132: The tools version "2.0" is unrecognized. Available tools versions are "14.0", "4.0".
	gyp ERR! build error
	gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
	gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
	gyp ERR! stack at emitTwo (events.js:87:13)
	gyp ERR! stack at ChildProcess.emit (events.js:172:7)
	gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
	gyp ERR! System Windows_NT 6.3.9600
	gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
	gyp ERR! cwd C:\Parse\node_modules\kerberos
	gyp ERR! node -v v4.4.4
	gyp ERR! node-gyp -v v3.3.1
	gyp ERR! not ok
	kerberos@0.0.21 node_modules\kerberos
	└── nan@2.3.3
	express@4.11.2 node_modules\express
	├── utils-merge@1.0.0
	├── media-typer@0.3.0
	├── methods@1.1.2
	├── fresh@0.2.4
	├── cookie@0.1.2
	├── range-parser@1.0.3
	├── finalhandler@0.3.3
	├── serve-static@1.8.1
	├── parseurl@1.3.1
	├── content-disposition@0.5.0
	├── escape-html@1.0.1
	├── cookie-signature@1.0.5
	├── merge-descriptors@0.0.2
	├── vary@1.0.1
	├── depd@1.0.1
	├── path-to-regexp@0.1.3
	├── qs@2.3.3
	├── on-finished@2.2.1 (ee-first@1.1.0)
	├── debug@2.1.3 (ms@0.7.0)
	├── send@0.11.1 (destroy@1.0.3, ms@0.7.0, mime@1.2.11)
	├── proxy-addr@1.0.10 (forwarded@0.1.0, ipaddr.js@1.0.5)
	├── etag@1.5.1 (crc@3.2.1)
	├── accepts@1.2.13 (negotiator@0.5.3, mime-types@2.1.11)
	└── type-is@1.5.7 (mime-types@2.0.14)
	parse@1.8.5 node_modules\parse
	├── xmlhttprequest@1.8.0
	├── ws@1.1.0 (options@0.0.6, ultron@1.0.2)
	└── babel-runtime@5.8.38 (core-js@1.2.6)
	parse-server@2.2.10 node_modules\parse-server
	├── parse-server-simple-mailgun-adapter@1.0.0
	├── bcrypt-nodejs@0.0.3
	├── intersect@1.0.1
	├── winston-daily-rotate-file@1.1.0
	├── mime@1.3.4
	├── tv4@1.2.7
	├── deepcopy@0.6.1
	├── colors@1.1.2
	├── commander@2.9.0 (graceful-readlink@1.0.1)
	├── lru-cache@4.0.1 (pseudomap@1.0.2, yallist@2.0.0)
	├── ws@1.1.0 (options@0.0.6, ultron@1.0.2)
	├── redis@2.5.3 (double-ended-queue@2.1.0-0, redis-commands@1.2.0, redis-parser@1.3.0)
	├── winston@2.2.0 (cycle@1.0.3, isstream@0.1.2, stack-trace@0.0.9, eyes@0.1.8, async@1.0.0, pkginfo@0.3.1, colors@1.0.3)
	├── body-parser@1.15.1 (bytes@2.3.0, content-type@1.0.2, depd@1.1.0, qs@6.1.0, on-finished@2.3.0, raw-body@2.1.6, http-errors@1.4.0, debug@2.2.0, iconv-lite@0.4.13, type-is@1.6.13)
	├── express@4.13.4 (utils-merge@1.0.0, methods@1.1.2, content-type@1.0.2, vary@1.0.1, range-parser@1.0.3, parseurl@1.3.1, escape-html@1.0.3, array-flatten@1.1.1, cookie-signature@1.0.6, merge-descriptors@1.0.1, content-disposition@0.5.1, fresh@0.3.0, etag@1.7.0, serve-static@1.10.2, path-to-regexp@0.1.7, cookie@0.1.5,depd@1.1.0, qs@4.0.0, on-finished@2.3.0, finalhandler@0.4.1, proxy-addr@1.0.10,debug@2.2.0, accepts@1.2.13, type-is@1.6.13, send@0.13.1)
	├── parse-server-fs-adapter@1.0.0 (parse-server-conformance-tests@1.0.0, jasmine
	@2.4.1)
	├── mongodb@2.1.19 (es6-promise@3.0.2, readable-stream@1.0.31, mongodb-core@1.3.19)
	├── multer@1.1.0 (object-assign@3.0.0, append-field@0.1.0, xtend@4.0.1, on-finished@2.3.0, type-is@1.6.13, mkdirp@0.5.1, concat-stream@1.5.1, busboy@0.2.13)
	├── request@2.72.0 (tunnel-agent@0.4.3, oauth-sign@0.8.2, aws-sign2@0.6.0, forever-agent@0.6.1, is-typedarray@1.0.0, caseless@0.11.0, stringstream@0.0.5, aws4@1.4.1, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.0, tough-cookie@2.2.2, qs@6.1.0, node-uuid@1.4.7, combined-stream@1.0.5, mime-types@2.1.11, form-data@1.0.0-rc4, bl@1.1.2, hawk@3.1.3, http-signature@1.1.1, har-validator@2.0.6)
	├── mailgun-js@0.7.11 (tsscmp@1.0.1, q@1.4.1, inflection@1.7.2, async@1.5.2, path-proxy@1.0.0, debug@2.2.0, form-data@1.0.0-rc4, proxy-agent@2.0.0)
	├── parse-server-push-adapter@1.0.4 (npmlog@2.0.4, apn@1.7.5, node-gcm@0.14.0)
	├── parse-server-s3-adapter@1.0.2 (aws-sdk@2.3.14)
	├── lodash@4.12.0
	├── babel-polyfill@6.9.0 (babel-regenerator-runtime@6.5.0, core-js@2.4.0)
	└── babel-runtime@6.9.0 (core-js@2.4.0)
	C:\Parse>

view raw installation.cmd hosted with ❤ by GitHub

During the installation I hit a small bump with the following error message:
MSBUILD : error MSB4132: The tools version "2.0" is unrecognized. Available tools versions are "14.0", "4.0".

To overcome this issue, just install the MSBuild Tools from VS2013. This can be found here. Now we are ready to start our PARSE server.

Starting PARSE server.
Remember to start mongoDB first here as the server was restarted from installing Pyhton. MongoDB should show that its waiting for connection. Here are some logs when the system is up and running:

	(3 connections now open)
	2016-05-21T21:37:38.966+0100 I NETWORK [initandlisten] connection accepted from 127.0.0.1:64672 #533 (4 connections now open)
	2016-05-21T21:39:07.005+0100 I NETWORK [conn531] end connection 127.0.0.1:64670 (3 connections now open)
	2016-05-21T21:39:07.006+0100 I NETWORK [conn530] end connection 127.0.0.1:64661 (3 connections now open)
	2016-05-21T21:39:07.016+0100 I NETWORK [conn532] end connection 127.0.0.1:64671 (1 connection now open)
	2016-05-21T21:39:08.019+0100 I NETWORK [initandlisten] connection accepted from 127.0.0.1:64675 #534 (2 connections now open)
	2016-05-21T21:39:38.968+0100 I NETWORK [conn533] end connection 127.0.0.1:64672 (1 connection now open)

view raw mongod.cmd hosted with ❤ by GitHub

Configure PARSE:
Open the file index.js under C:\Parse and edit the sections appId and masterKey

	// Example express application adding the parse-server module to expose Parse
	// compatible API routes.
	var express = require('express');
	var ParseServer = require('parse-server').ParseServer;
	var path = require('path');
	var databaseUri = process.env.DATABASE_URI || process.env.MONGODB_URI;
	if (!databaseUri) {
	console.log('DATABASE_URI not specified, falling back to localhost.');
	}
	var api = new ParseServer({
	databaseURI: databaseUri || 'mongodb://localhost:27017/dev',
	cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
	appId: process.env.APP_ID || 'thunderParse',
	masterKey: process.env.MASTER_KEY || 'NzIxNTc2Mzk5NDI5MjE4DmNzNkZTA4ZGM3NzRlNg==', //Add your master key here. Keep it secret!
	serverURL: process.env.SERVER_URL || 'http://localhost:1337/parse', // Don't forget to change to https if needed
	liveQuery: {
	classNames: ["Posts", "Comments"] // List of classes to support for query subscriptions
	}
	});

view raw index.js hosted with ❤ by GitHub

In my case, I mentioned the appId as 'thunderParse' and the masterKey as a nice key (base64 string).

Run PARSE server via npm:

	C:\Parse>npm start
	> parse-server-example@1.4.0 start C:\Parse
	> node index.js
	DATABASE_URI not specified, falling back to localhost.
	parse-server-example running on port 1337.

view raw parse.cmd hosted with ❤ by GitHub

Once configured, run in the same command line the command npm start.

Now parse is up and running and is ready for requests.

Configuring and Starting PARSE Dashboard.
Now that our PARSE server is running, we can configure and start the PARSE dashboard which is a web base application to manage our PARSE apps.

To get PARSE dashboard, you only need to type the following from npm:

	Your environment has been set up for using Node.js 4.4.4 (x64) and npm.
	C:\Parse-dashboard>npm install -g parse-dashboard
	C:\Users\Administrator\AppData\Roaming\npm\parse-dashboard -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\parse-dashboard\bin\parse-dashboardparse-dashboard@1.0.11 C:\Users\Administrator\AppData\Roaming\npm\node_modules\parse-dashboard
	├── basic-auth@1.0.4
	├── commander@2.9.0 (graceful-readlink@1.0.1)
	├── express@4.13.4 (escape-html@1.0.3, array-flatten@1.1.1, utils-merge@1.0.0, cookie-signature@1.0.6, merge-descriptors@1.0.1, content-type@1.0.2, methods@1.1.2, vary@1.0.1, cookie@0.1.5, etag@1.7.0, path-to-regexp@0.1.7, fresh@0.3.0, serve-static@1.10.2, parseurl@1.3.1, content-disposition@0.5.1, range-parser@1.0.3,depd@1.1.0, qs@4.0.0, on-finished@2.3.0, finalhandler@0.4.1, debug@2.2.0, proxy-addr@1.0.10, send@0.13.1, accepts@1.2.13, type-is@1.6.13)
	├── package-json@2.3.2 (registry-url@3.1.0, semver@5.1.0, rc@1.1.6, got@5.6.0)
	└── json-file-plus@3.3.0 (node.extend@1.1.5, is@3.1.0, promiseback@2.0.2)
	C:\Parse-dashboard>parse-dashboard --appId thunderParse --masterKey NzIxNTc2Mzk5NDI5MjE4DmNzNkZTA4ZGM3NzRlNg== --serverURL "http://localhost:1337/parse" -
	-appName thunderParse
	The dashboard is now available at http://0.0.0.0:4040/

view raw parse-dashboard.cmd hosted with ❤ by GitHub

Now we can go to localhost:4040/apps and we will see our application described there:

Testing our self-hosted PARSE server.
Now is the time to test our self-hosted PARSE server. To test it out, we just need to use curl or any other mechanism that we like. I've used curl and Delphi as I already had some libraries prepared for it. Here is the command with curl:

	curl -X POST \
	-H "X-Parse-Application-Id: thunderParse" \
	-H "Content-Type: application/json" \
	-d '{"version":"0.0","Id":"1","photos":100,"views":100,"likes":100,"comments":100}' \
	http://localhost:1337/parse/classes/Instances

view raw curl.cmd hosted with ❤ by GitHub

And here with Delphi:

	/**
	* @Author: Jordi Corbilla
	* (c) Copyright by Jordi Corbilla.
	**/
	//Usage -> UpdateClient('1', 100, 100, 100, 100, '0.0');
	function UpdateClient(id: string; photos, views, likes, comments: integer; version: string): boolean;
	var
	IdHTTP: TIdHTTP;
	IdIOHandler: TIdSSLIOHandlerSocketOpenSSL;
	response : string;
	JsonToSend: TStringStream;
	begin
	JsonToSend := TStringStream.Create('{"version":"'+version+'","Id":"'+id+'","photos":'+photos.ToString+',"views":'+views.ToString+',"likes":'+likes.ToString+',"comments":'+comments.ToString+'}');
	try
	IdIOHandler := TIdSSLIOHandlerSocketOpenSSL.Create(nil);
	IdIOHandler.ReadTimeout := IdTimeoutInfinite;
	IdIOHandler.ConnectTimeout := IdTimeoutInfinite;
	IdHTTP := TIdHTTP.Create(nil);
	try
	IdHTTP.IOHandler := IdIOHandler;
	IdHTTP.Request.Connection := 'Keep-Alive';
	IdIOHandler.SSLOptions.Method := sslvSSLv23;
	IdHTTP.Request.CustomHeaders.Clear;
	IdHTTP.Request.CustomHeaders.Values['X-Parse-Application-Id'] := 'thunderParse';
	IdHTTP.Request.ContentType := 'application/json';
	response := IdHTTP.Post('http://localhost:1337/parse/classes/Instances', JsonToSend);
	response := response.Replace(AnsiChar(#10), '');
	result := (response.Contains('createdAt'));
	finally
	IdHTTP.Free;
	end;
	finally
	IdIOHandler.Free;
	JsonToSend.Free;
	end;
	end;

view raw DelphiPARSEServercall.pas hosted with ❤ by GitHub

And here are the results of the App writing to Parse server:

Next step is to bring this online and host it somewhere else like Heroku, AWS, AZure or Scalingo.

I hope you find this useful.

Jordi