mervynteo / meteor-login-package

A custom login package for meteor js

Meteor Login Package

This is a custom login package for Meteor.js using the core accounts-password and accounts-twitter packages.

This package differs from the accounts-ui package, as it has a built in route that goes to a /login.html page, and a better UI. Personally, I'm not a fan of using bootstrap, and the accounts-ui package that offeres a dropdown style account login/register functionality didn't suit my needs.

Check out a demo here.

Usage:

The usage is the same as the accounts-ui package. Simply include a {{> loginButtons}} template block somewhere. Since this package uses Iron:Router, you will probably have some sort of layout template. So include it there, or inside of a {{> header}} partial.

The only additional step is include an {{> errors}} template block helper somewhere in your layout template as well. This will allow the user to see any login/registration errors in your application. The errors are styled to be fixed position at the top. Style accordingly.

Configuration:

This package currently comes with just a couple of custom configuration settings. More to come, though. As of now, you can set the "afterLoginRoute", which routes the user some place after a successfull login (or if they are currently logged in and go to '/login'), and you can disable login with twitter. Simply call CustomLogin.config inside of a Meteor.startup callback on the client side. Like this:

Meteor.startup(function(){
	CustomLogin.config({
		afterLoginRoute: '/dashboard', 		//defaults to '/dashboard'
		endbleTwitterLogin: fals		//defaults to true
	})
})

With Twitter:

This package includes login with twitter using the twitter oauth flow package, so you don't need any API keys. However, should you have your own twitter app you'd like to use, simply include the public and private keys in a settings.json file inside the root directory of your app. like this:

{
  "twitter": {
		"public": "<insert public key here>",
		"private":"<insert private key here>"
	}
}

Make sure when you run or deploy meteor, you use the --settings option. Like this:

$ meteor run --setings settings.json