pages
An unofficial sidekick for AngularJS / (and optionally) Node.js applications. It's a developer's framework.
Pre-reqs
Just make it so.
- OSX
- Node.js, version 0.10.12.
- Ruby For Terminal Notifier
- Java For node-minify
- Terminal Notifier
Also, because Pages manages Bower assets for you (and thus interacts with the filesystem), you'll probably want to run ulimit -n 10000
or face the error Error: spawn EMFILE
.
Install
sudo npm install -g pages
Note: Pages doesn't require any dependency but itself to be installed globally.
Usage (simple)
Pages has a CLI; it's how you use it!
What can you do with Pages?
pages help
todo Add help when finished.
Create a Pages application:
pages generate --type=app --name="My Pages App"
This generates a non-compiled application from a default or configured skeleton.
Note: The name
option is sanitized to my-pages-app
.
Run, compile, and watch for changes in a Pages application for development
:
cd my-pages-app
pages run --port=3000 --browser=chrome
This runs the Pages application compiler on port 3000
, watching for changes to CoffeeScripts, Jade templates, and dependencies; Google Chrome's first browser tab is automatically refreshed after bundling (compiling/downloading assets).
Note: By default (not specifying the option), Pages runs applications on port 80
. If you do not have access to port 80
, it will hang.
Compile/concat/minify/run a Pages application for production
:
cd my-pages-app
pages start --port=3000 --browser=chrome
Note: The same default port assignments apply from the CLI command pages run
, but a specified browser will refresh just once after the build is done.
See the wiki for more!