Skip to content
PEAN.JS - Full-Stack JavaScript Using PostgreSQL, Express, AngularJS, and Node.js
JavaScript HTML Other
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
config fix(config): Change Express "sessionExpiration" config reference Oct 18, 2016
modules fix(users): Remove orphaned commas Oct 18, 2016
public Remove executable bit when not necessary Feb 16, 2015
scripts Remove MongoDB/Mongoose references Jan 16, 2016
.bowerrc formatting reboot (space-2 and consistency) Jul 31, 2015
.csslintrc formatting reboot (space-2 and consistency) Jul 31, 2015
.editorconfig Changed .html files to have 2 spaces instead of tabs Aug 18, 2015
.eslintrc Add ESLint support Oct 17, 2015
.gitignore feat(config): Local env configurations Nov 29, 2015
.jshintrc Closes #202 - if user does not authorize email scope, email will not … Aug 23, 2015
.slugignore Add missing newline at the end of text files Feb 16, 2015
.travis.yml Remove MongoDB/Mongoose references Jan 16, 2016
CHANGELOG.md [docs] Changelog and updating package.json file for 0.4.2 release Nov 15, 2015
CONTRIBUTING.md Merge remote-tracking branch 'upstream/master' Jan 16, 2016
LICENSE.md Move license to it's own file. Easier to see what the license is when… Apr 14, 2014
Procfile Remove executable bit when not necessary Feb 16, 2015
README.md feat(config): Modify configuration options Mar 16, 2016
bower.json Change Docker definitions Jan 21, 2016
gruntfile.js Remove MongoDB/Mongoose references Jan 16, 2016
gulpfile.js fix(config): Change Gulp unit test configuration Mar 31, 2016
karma.conf.js
manifest.yml
package.json feat(config): Modify configuration options Mar 16, 2016
protractor.conf.js adding protractor options to fix travis failing Oct 6, 2015
server.js Finish core conversion Jan 15, 2016
test.js adding support for coveralls integration for mean.js to report live p… Aug 21, 2015

README.md

#PEAN.JS

PEAN.JS is a full-stack JavaScript open-source solution, which provides a solid starting point for PostgreSQL, Node.js, Express, and AngularJS based applications. The idea is to solve the common issues with connecting those frameworks, build a robust framework to support daily development needs, and help developers use better practices while working with popular JavaScript components.

Before You Begin

Before you begin we recommend you read about the basic building blocks that assemble a PEAN.JS application:

Prerequisites

Make sure you have installed all of the following prerequisites on your development machine:

$ npm install -g bower
  • Grunt - You're going to use the Grunt Task Runner to automate your development process. Make sure you've installed Node.js and npm first, then install grunt globally using npm:
$ npm install -g grunt-cli
  • Sass - You're going to use Sass to compile CSS during your grunt task. Make sure you have ruby installed, and then install Sass using gem install:
$ gem install sass
$ npm install -g grunt-cli
  • Gulp - (Optional) You may use Gulp for Live Reload, Linting, and SASS or LESS.
$ npm install gulp -g

Downloading PEAN.JS

There are several ways you can get the PEAN.JS boilerplate:

Cloning The GitHub Repository

The recommended way to get PEAN.js is to use git to directly clone the PEAN.JS repository:

$ git clone https://github.com/StetSolutions/pean.git peanjs

This will clone the latest version of the PEAN.JS repository to a peanjs folder.

Downloading The Repository Zip File

Another way to use the PEAN.JS boilerplate is to download a zip copy from the master branch on GitHub. You can also do this using wget command:

$ wget https://github.com/StetSolutions/pean/archive/master.zip -O peanjs.zip; unzip peanjs.zip; rm peanjs.zip

Don't forget to rename pean-master after your project name.

Quick Install

Once you've downloaded the boilerplate and installed all the prerequisites, you're just a few steps away from starting to develop your PEAN application.

The first thing you should do is install the Node.js dependencies. The boilerplate comes pre-bundled with a package.json file that contains the list of modules you need to start your application. To learn more about the modules installed visit the NPM & Package.json section.

To install Node.js dependencies you're going to use npm again. In the application folder, run this from the command-line:

$ npm install

This command does a few things:

  • First it will install the dependencies needed for the application to run.
  • If you're running in a development environment, it will then also install development dependencies needed for testing and running your application.
  • Finally, when the install process is over, npm will initiate a bower install command to install all the front-end modules needed for the application.

Running Your Application

The first thing you will need to do is supply your PostgreSQL credentials.

To do this, duplicate 'config/env/local.example.js' and rename the file 'config/env/local-development.js' (as instructed in the example file itself).

If you have not done so already, create a PostgreSQL database (our example uses a database named 'pean_dev').

Uncomment 'module.exports' in the 'local-development.js' file you just created and replace the 'db.options' properties with your own PostgreSQL database name, username and password.

Make sure that 'db.force' is set to 'true' (as in the example). When the Sequelize option 'force' is set to 'true', all tables are dropped and recreated everytime the server is started/restarted. Additionally, any roles defined in your configuration will be added to the 'Roles' table by the application.

Now just run your application using Grunt.

In the application folder, run this from the command-line:

$ grunt

or in 'debugging' mode:

$ grunt debug

Your application should run on port 3000 with the development environment configuration, so in your browser just go to http://localhost:3000

That's it! Your application should be running. To proceed with your development, check the other sections in this documentation.

If you encounter any problems, try the Troubleshooting section.

  • Explore config/env/development.js for development environment configuration options.
  • Set 'force' to 'false' if you want to preserve your table data on server restart.

Running in Production mode

To run your application with production environment configuration, execute grunt as follows:

$ grunt prod
  • Explore config/env/production.js for production environment configuration options.

Running with User Seed

To have default account(s) seeded at runtime:

In Development:

DB_SEED=true grunt

It will try to seed the users 'user' and 'admin'. If one of the user already exists, it will display an error message on the console.

Just grab the passwords from the console.

In Production:

DB_SEED=true grunt prod

This will seed the admin user one time if the user does not already exist. You have to copy the password from the console and save it.

To 'force' a complete refresh of the DB, set the Sequelize 'force' option:

DB_FORCE=true DB_SEED=true grunt

Running with TLS (SSL)

Application will start by default with secure configuration (SSL mode) turned on and listen on port 8443. To run your application in a secure manner you'll need to use OpenSSL and generate a set of self-signed certificates. Unix-based users can use the following command:

$ sh ./scripts/generate-ssl-certs.sh

Windows users can follow instructions found here. After you've generated the key and certificate, place them in the config/sslcerts folder.

Finally, execute grunt's prod task grunt prod

  • enable/disable SSL mode in production environment change the secure option in config/env/production.js

Testing Your Application

You can run the full test suite included with PEAN.JS with the test task:

$ grunt test

This will run both the server-side tests (located in the app/tests/ directory) and the client-side tests (located in the public/modules/*/tests/).

To execute only the server tests, run the test:server task:

$ grunt test:server

And to run only the client tests, run the test:client task:

$ grunt test:client

And to run only the "end to end" tests, run the test:e2e task:

grunt test:e2e

Running your application with Gulp

After the install process, you can easily run your project with:

$ gulp

or

$ gulp default

The server is now running on http://localhost:3000 if you are using the default settings.

Running Gulp Development Environment

Start the development environment with:

$ gulp dev

Running in Production mode

To run your application with production environment configuration, execute gulp as follows:

$ gulp prod

Testing Your Application with Gulp

Using the full test suite included with PEAN.JS with the test task:

Run all tests

$ gulp test

Run server tests

gulp test:server

Run client tests

gulp test:client

Run e2e tests

gulp test:e2e

Getting Started With PEAN.JS

You have your application running, but there is a lot of stuff to understand. We recommend you go over the Official MEAN Documentation. In the docs we'll try to explain both general concepts of MEAN components and give you some guidelines to help you improve your development process. We tried covering as many aspects as possible, and will keep it updated by your request. You can also help us develop and improve the documentation by checking out the gh-pages branch of this repository.

Community

Contributing

We welcome pull requests from the community! Just be sure to read the contributing doc to get started.

Credits

Inspired by the great work of Madhusudhan Srinivasa The MEAN name was coined by Valeri Karpov

License

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

You can’t perform that action at this time.