Boilerplates can be a huge time sink to maintain and I've decieded to archive this project.
Thanks for your interest in my projects.
A user system API starter. Bring your own front-end.
- Login system with forgot password and reset password
- Abusive login attempt detection
- User roles for accounts and admins
- Admins only notes and status history for accounts
- Admin groups with shared permissions
- Admin level permissions that override group permissions
Frame is built with the hapi framework. We're using MongoDB as a data store.
Frame is only a restful JSON API. If you'd like a ready made front-end, checkout Aqua. Or better yet, fork this repo and build one on top of Frame.
url | username | password |
---|---|---|
https://getframe.herokuapp.com/ | root | root |
https://getframe.herokuapp.com/documentation |
Postman is a great tool for testing and developing APIs. See the wiki for details on how to login.
You need Node.js >=8.x
and you'll need a
MongoDB >=2.6
server running.
$ git clone https://github.com/jedireza/frame.git
$ cd frame
$ npm install
Simply edit config.js
. The configuration uses
confidence
which makes it easy to
manage configuration settings across environments. Don't store secrets in
this file or commit them to your repository.
Instead, access secrets via environment variables. We use
dotenv
to help make setting local
environment variables easy (not to be used in production).
Simply copy .env-sample
to .env
and edit as needed. Don't commit .env
to your repository.
WARNING: This will clear all data in the following MongoDB collections if
they exist: accounts
, adminGroups
, admins
, authAttempts
, sessions
,
statuses
, and users
.
$ npm run first-time-setup
# > [email protected] first-time-setup /home/jedireza/projects/frame
# > node first-time-setup.js
# MongoDB URL: (mongodb:https://localhost:27017/frame)
# Root user email: [email protected]
# Root user password:
# Setup complete.
$ npm start
# > [email protected] start /home/jedireza/projects/frame
# > ./node_modules/nodemon/bin/nodemon.js -e js,md server
# 09 Sep 03:47:15 - [nodemon] v1.10.2
# ...
Now you should be able to point your browser to https://127.0.0.1:9000/ and see the welcome message.
nodemon
watches for changes in server
code and restarts the app automatically.
$ npm run inspect
# > [email protected] inspect /home/jedireza/projects/frame
# > nodemon --inspect -e js,md server.js
# [nodemon] 1.14.12
# [nodemon] to restart at any time, enter `rs`
# [nodemon] watching: *.*
# [nodemon] starting `node --inspect server.js`
# Debugger listening on ws:https://127.0.0.1:9229/3d706d9a-b3e0-4fc6-b64e-e7968b7f94d0
# For help see https://nodejs.org/en/docs/inspector
# 180203/193534.071, [log,info,mongodb] data: HapiMongoModels: successfully connected to the db.
# 180203/193534.127, [log,info,mongodb] data: HapiMongoModels: finished processing auto indexes.
# Server started on port 9000
Once started with the debuger you can open Google Chrome and go to chrome:https://inspect. See https://nodejs.org/en/docs/inspector/ for more details.
$ node server.js
Unlike $ npm start
this doesn't watch for file changes. Also be sure to set
these environment variables in your production environment:
NODE_ENV=production
- This is important for many different optimizations.NPM_CONFIG_PRODUCTION=false
- This tells$ npm install
to not skip installingdevDependencies
, which we may need to run the first time setup script.
Any issues or questions (no matter how basic), open an issue. Please take the initiative to read relevant documentation and be pro-active with debugging.
Contributions are welcome. If you're changing something non-trivial, you may want to submit an issue before creating a large pull request.
Lab is part of the hapi ecosystem and what we use to write all of our tests.
$ npm test
# > [email protected] test /home/jedireza/projects/frame
# > lab -c -L
# ..................................................
# ..................................................
# ..................................................
# ..............
# 164 tests complete
# Test duration: 14028 ms
# No global variable leaks detected
# Coverage: 100.00%
# Linting results: No issues
If you'd like to run a specific test or subset of tests you can use the
test-server
npm script.
You specificy the path(s) via the TEST_TARGET
environment variable like:
$ TEST_TARGET=test/server/web/main.js npm run test-server
MIT
What you build with Frame is more important than Frame.