CarlPapa is a recipe app built in July 2015 with Carl Brown (carlbrown64 on GitHub). Its README promises “the best damn cooking app you would ever want!!!!” It keeps a list of recipes, each with a name, its ingredients and instructions, and lets you add, edit and delete them.
The repository started on July 2 with an Express server and an AngularJS client generated by Yeoman. Carl wrote most of the app from there: the recipe views and controllers, the recipe API, and a JWT login that was still in progress when the commits stopped on July 31, 2015.
What it does
At its July 24 commit, the client and the API work end to end:
- The home view lists every recipe by name, with an Add Recipe button.
- The add form has a name, ingredients and instructions. When you leave the last ingredient field with something in it, a new empty one appears. A recipe needs a name, instructions and at least one ingredient before it’s sent.
- Clicking a recipe opens it for editing. Save Recipe turns the button into “Recipe Saved!” for five seconds, and Delete Recipe removes the recipe and goes back to the list.


How it’s built
The client started from generator-angular 0.11.1, with a Gruntfile for serving, building and testing (Compass for Sass, Karma with PhantomJS) and Bower for the front-end libraries. ui-router was in place from the first commit, with states for the list, add and edit views. Materialize 0.97 gives it the underlined fields and teal buttons, on top of Bootstrap’s Sass from the generator. The controllers talk to the API with $http.
The server is Express 4.0 with Mongoose 3.6. At the July 24 commit it’s a REST API at /api/recipe that lists and creates recipes, and reads, updates and deletes one by id.
Where it stopped
The last week added login. The server gained /api/createAccount and /api/authenticate, which signs a token with jsonwebtoken, and a middleware that guards every route after them. The client gained a login view that signs in through Satellizer.

At the last commit, signing in works and Satellizer stores the token. But the recipe routes had become empty stubs in the rewrite, the client now asks for recipes at /api/ instead of /api/recipe/, and Satellizer sends the token in an Authorization header that the middleware doesn’t read, so the recipe list comes back 403 with “No token provided.” The commit that started the rewrite says so: “updated express router. Auth is broken”. In this version, passwords are also stored and compared as plain text.
The same token check turns up a month later in material.chef, the next recipe app here, this time with a React and Flux client and bcrypt-hashed passwords.
Running it today
- Server. With Node 6, run
npm installinserver, add aconfig.js(git ignores it) with a MongoDBdbURL and asecret, and runnode server.js. It listens on port 9090, which the client expects. MongoDB 3.6 still works with Mongoose 3.6. - Libraries. Install the Bower packages at the versions their ranges resolved to in July 2015: AngularJS 1.4.3, ui-router 0.2.15, Materialize 0.97.0, bootstrap-sass 3.3.5, Satellizer 0.11.3 and jQuery 2.1.4. AngularJS 1.4 matters: the controllers use
$http’s.success(), which AngularJS 1.6 removed, and^1.3.0now resolves to 1.8. - Client.
grunt serveneeds Ruby for Compass. Compilingapp/styles/main.scsswith Dart Sass, withbower_componentsas a load path, into.tmp/stylesworks, and then any static server can serve.tmp,bower_componentsandappthe way the Gruntfile’s connect task does.
To see the working app, check out commit f91adbc. The last commit shows the login screen and an empty list.
The creation date shown here is the GitHub repository’s UTC creation date. The screenshots were captured by running the July 24, 2015 commit locally from its source with Node 6, MongoDB 3.6 and recipes typed in for the captures, and the code card shows the server’s source at the last commit.