Following new API and features are added into this release:
- 'getTodos' - This will return all the Todo's mapped to the logged in User | Only logged in User.
- 'newTodo' - This api will create a new Todo mapped to the logged in User. | Only logged in User.
- 'getTodos' - This will return all the Todo's mapped to the logged in User | Only logged in User.
- 'newTodo' - This api will create a new Todo mapped to the logged in User. | Only logged in User.
Dependenices:
One time dependencies (you only need to do these the first time you set up this app). If you have set up this app before, skip to step 4.
-
Download node.js if you have not already http://nodejs.org/. You can confirm that node is successfully installed on your machine by opening up Terminal and typing 'node'. If you don't get an error, it's installed! You can exit the node process with Ctrl+c. If you already have node, no action needed.
-
Download and install the Heroku Toolbelt https://toolbelt.heroku.com, this will give you the Heroku CLI (command line interface). If you already have the Heroku Toolbelt, you can skip this step.
-
Set up an account at https://heroku.com. You will be asked to enter a credit card, but the app we are doing will not incur any charges (they just need a card on file). In fact, all Heroku apps have a starter/free level. If you already have a Heroku account, you can skip this step.
Every time dependencies (do these EVERY time you set up a new app using this boilerplate)
- Download this boilerplate repo and navigate into the code directory with Terminal. To download it, click "Download Zip" at the repo... (do not clone it).
cd path/to/this/code/directory
-
Run npm install to get all required libraries.
npm install -
We now need to setup Git, a Github repository, and a Heroku app.
First we'll start tracking it with Git:
git init
git add .
git commit -am "init commit"
- Create the Github Repo
Go to Github and create a new repo by clicking "New Repo" in top right. You only need to create a repo once per project. You will keep pushing your latest code to this repo.
Once you've created the repo, choose the option: "…or push an existing repository from the command line"
Run the following in Terminal:
git remote add origin insertYourUniqueURLHere
git push -u origin master
The first command associates the Github repo to your app (so it knows which Github repo to push our code to). The second command actually pushes your code to the repo.
You can now refresh the repo page at Github and you will see the code there.
-
Create the Heroku app
heroku create
NOTE: if it is your very FIRST time setting up a Heroku app, you will need to upload a public key to Heroku. See http://stackoverflow.com/a/6059231. As explained in that StackOverlow link, if you don't yet have a public key, you'll be prompted to add one.
-
Now that your heroku app is set-up, you can rename it whenever you like (now or in the future):
heroku rename your-new-name
Your app will now be available at your-app-name.herokuapp.com
You can always open your app with the command:
heroku open
Heroku has many nice add-ons that make it easier to set-up an app. For example, the MongoLabs add-on gives you a MongoDB database with a single command.
-
Add MongoLabs Starter MongoDB to your heroku app:
heroku addons:create mongolab
If you log-in to your heroku dashboard at https://heroku.com, you'll now see this as an add-on. Click on the 'MongoLab' link to see your database.
-
Get the Heroku MongoLab connection string into an .env file.
heroku config --shell | grep MONGODB_URI >> .env
Your connection string to MongoDB will now be in a .env file now (go have a look at the .env file). Your app connects to this database in the app.js file:
app.db = mongoose.connect(process.env.MONGODB_URI);
Your .env file is a secret config file that holds key app variables like this MongoDB URI string, and other things like 3rd Party API secrets and keys. It is specified in the .gitignore file, which means the .env file will not be tracked by .git and not available for others to see on github (this is good).
-
We're ready to go! Run npm start to start your server.
npm start
You can stop the server with Ctrl+c.
However, a slight annoyance here is that every time you change your code, you'll need to stop and restart your server.
A better option is to auto restart your server after you make some changes to your code. To do this, install Nodemon. Nodemon will watch your files and restart the server for you whenever your code changes.
Install Nodemon (you only need to do this once, and then it will be installed globally on your machine). In Terminal type,
npm install -g nodemon
Then, you can start the app with:
nodemon
Once you do this step, you should always start your app with nodemon
-
Open web browser to http://localhost:3000 to view the web app.
-
Stop the web server press Ctrl+c in the Terminal window.
As you make changes, you'll want to periodically push your updated code base to both Github and to Heroku (where it is publicly hosted).
To get your updated code to Heroku, you'll need to:
git add .
git commit -m "your commit message"
git push heroku master
To get your updated code to Github, you'll need to:
git add .
git commit -am "your commit message"
git push origin master
You don't need to double add and double commit though. So the following will work:
git add .
git commit -am "your commit message"
git push origin master
git push heroku master
This app uses the following libraries and concepts:
ExpressJS (http://expressjs.com/) is a popular framework for building web applications in NodeJS.
Web service APIs that adhere to the REST architectural constraints are called RESTful APIs (http://en.wikipedia.org/wiki/Representational_state_transfer#Applied_to_web_services). HTTP based RESTful APIs are defined with these aspects:
- base URI, such as http://example.com/resources/ or http://example.com/api/
- an Internet media type for the data. We are using JSON, but it can be any other valid Internet media type (e.g. XML, Atom, microformats, images, etc.)
- standard HTTP methods (e.g., GET, PUT, POST, or DELETE) and standardized and descriptive naming in API endpoints
Typical REST queries will look like:
- CREATE - http://example.com/api/create (POST)
- RETRIEVE 1 - http://example.com/api/get/:id (GET)
- RETRIEVE ALL - http://example.com/api/get (GET)
- UPDATE - http://example.com/api/update/:id (PUT)
- DELETE - http://example.com/api/delete/:id (DELETE)
The above are typically called API endpoints, and client applications interact with your API by sending requests to these endpoints. Remember, a client can be anything that can send an HTTP request, such as a browser, a mobile app, an Arduino Yun, etc.
Routing is how your app handles these incoming HTTP requests: performing the appropriate action and responding back to the client.
In node.js (using Express), this is done through executing a callback function. In human language:
when this request is received, perform this action, and respond back (usually with JSON).
For example:
// when the user requests the 'api/get' route, call a function that retrieves the data, and responds back
router.get('/api/get', function(req, res, next){
// step 1 - code to retrieve data
// step 2 - code to respond back with res.json();
})
A nice part about the ExpressJS framework (and nodejs in general) is the NPM system. NPM stands for Node Package Manager, and it allows us to include helpful node packages (libraries) that we can use in our app.
For example, open up package.json. You can see we are setting our dependent packages. When you run npm install, all of these dependencies will be installed in your node_modules folder.
package.json "dependencies": { "body-parser": "~1.13.2", "cookie-parser": "~1.3.5", "debug": "~2.2.0", "express": "~4.13.1", "mongoose": "^4.1.10", "morgan": "~1.6.1", "node-env-file": "^0.1.7", "serve-favicon": "~2.3.0" }
Dependencies are then declared in the app.js like:
var express = require('express');
var path = require('path');
var favicon = require('serve-favicon');
var logger = require('morgan');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');
var mongoose = require('mongoose');
var env = require('node-env-file');
To add a new node package, do the following in terminal:
npm install --save nameOfPackage
The --save flag will automatically include the package in package.json as a dependency.
heroku config --app restapi-express --shell | Findstr MONGODB_URI >> .env
let me help you out.