|
1 |
web: node lib/server.js |
|
1 2 3 4 5 6 7 8 |
var express = require('express'), app = express(), config = require('../config'); app.set('port', process.env.PORT || config.server.port || 3000); app.set('address', process.env.ADDRESS || config.server.address || 'localhost'); ... |
Here we’ll add a workers entry in the server section so we can specify the number of workers to fork.
Setting workers to ‘auto’ will assign number of CPUs, or 1 if the system has only 1 CPU.
You can also specify a specific number.
|
1 2 3 4 5 6 7 8 9 10 11 12 |
... production = { debug: false, sessions: false, server: { address: 'localhost', port: 3000, workers: 'auto' }, ... |
Helpers are stored in an object located at “dust.helpers”. To add another helper simply assign a function to a new key.
|
1 2 3 4 5 6 7 8 9 |
var dust = require('dustjs-linkedin'); // Make sure dust.helpers is an object before adding a new helper. if (!dust.helpers) dust.helpers = {}; dust.helpers.helloWorld = function(chunk, context, bodies, params) { return chunk.write('Hello World!'); }; |
You can then include your helper in your templates
|
1 2 |
<h1>Helper Example</h1> <p>{@helloWorld/}</p> |
We already have an onChange hook in our database adapter. All we need to do is remove the appropriate entry from the Dustjs cache.
|
1 2 3 4 5 6 7 8 9 10 11 |
var config = require('../../config'), // Load the db adapter according to the config DbAdapter = require('./' + config.db.type), db = new DbAdapter(), dust = require('dustjs-linkedin'); db.onChange = function(key) { delete dust.cache[key]; }; module.exports = db; |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
... production = { debug: false, sessions: false, server: { address: 'localhost', port: 3000 }, db: { type: 'redis' }, admin: { user: 'foo', password: 'bar' } }, ... |
We are going to use the Expressjs Basic Auth wrapper. All we need to do is instantiate an instance of the Basic Auth object and pass it in as an argument to each routes we want to protect.
We will be creating a basic database key list and html editor in this section. Part 6 will cover adding a security layer to the admin section.
CodeMirror is an in browser editor component with an easy to use API. A wide range of features and languages are supported.
|
1 |
git submodule add git://github.com/marijnh/CodeMirror.git public/codemirror |
We’ll need some icons for our toolbar. Using an icon font makes life easy.
http://fortawesome.github.com/Font-Awesome/
|
1 |
git submodule add git://github.com/FortAwesome/Font-Awesome.git public/font-awesome |
If you haven’t already, now would be a good time to look over the Dustjs templating language.
http://linkedin.github.com/dustjs/
|
1 |
npm install --save dustjs-linkedin dustjs-helpers mime |
|
1 |
mkdir lib/dust |
To keep things simple, I am limiting the interface to five functions.
|
1 |
mkdir lib/db |
The configuration file we are creating will be used to hold all of our application settings. These include things like the server port, database settings, and anything else we don’t want to hard code.
|
1 |
mkdir lib/helpers |
This is the first post in a series of post on building an asynchronous CMS using Node.js.
If you have not already used Expressjs, I recommend doing a quick read through of the
Expressjs Guide.