v1.5.26Published 7 years ago

This package has not had recent updates. Please investigate it's current state before committing to using it in your project.


This package provides the SignIn, SignUp, ForgotPassword, ChangePassword, and Logout pages.

Circle CI



meteor add clinical:active-entry


Entry Workflow States

Entry Workflow


Entry Flowchart

The following diagram represents the entry workflow that is being implemented in this package. This package is under active development, and is about half completed. Pull requests which help implement the following workflow will be fast-tracked and accepted into the package.



Routing API



Component API

{{> entrySignIn }}
{{> entrySignUp }}
{{> forgotPassword }}
{{> changePassword }}


ActiveEntry Configuration

3  ActiveEntry.configure({
4    logo: {
5      url: "/mini-circles.png",
6      displayed: true
7    },
8    signIn: {
9      displayFullName: true,
10      destination: "/table/users"
11    },
12    signUp: {
13      destination: "/table/users"
14    },
15    themeColors: {
16      primary: ""
17    }
18  });
22  Accounts.emailTemplates.siteName = "AwesomeSite";
23  Accounts.emailTemplates.from = "AwesomeSite Admin <>";
24  Accounts.emailTemplates.enrollAccount.subject = function (user) {
25      return "Welcome to Awesome Town, " +;
26  };
27  Accounts.emailTemplates.enrollAccount.text = function (user, url) {
28     return "You have been selected to participate in building a better future!"
29       + " To activate your account, simply click the link below:\n\n"
30       + url;
31  };  
33  Meteor.startup(function(){
34    process.env.MAIL_URL = 'smtp://';
35  })  

Alternatively, you may want to set the MAIL_URL via an external environment variable, particularly if you're using a SaaS hosting provider.

MAIL_URL = 'smtp://' meteor


Local Development

Simply clone the repository into your /packages directory. You can also specify the packages you want to develop locally in your .git-packages.json file, and use starrynight to fetch them.

# clone a single package into your application
git clone packages/active-entry

# fetch all the packages listed in git-packages.json
starrynight fetch


Quality Assurance Testing

There are two types of quality assurance tests you can run: verification and validation tests. Verification tests are similar to unit or integration tests; and can run either at the application or package level. Validation tests are application-wide, but often require commands exposed in packages. So you'll need to run the autoconfig command to scan the filesystem for validation commands. See for more details.

# install the testing utility
npm install -g starrynight

# verification testing (a.k.a. package-level unit/integration testing)
starrynight run-tests --type package-verification

#to run validation tests, you'll need an ``.initializeUsers()`` function
meteor add clinical:accounts-housemd

#validation testing (a.k.a. application acceptance/end-to-end testing)
starrynight autoscan
starrynight run-tests --type validation



See our notes on contributing.



MIT License