User management in each new app is a pain. This is the last time you should be doing it
Python HTML CSS Mako Ruby JavaScript
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
alembic Fix typo. Jul 20, 2016
lastuser_core Handle null scope Aug 24, 2016
lastuser_ui Switch to ua_parser for more reliable UA detection Sep 7, 2015
tests Fix test Mar 19, 2014
.gitignore Include the general static folder created by baseframe in .gitignore Mar 15, 2015
.travis.yml Update .travis.yml Aug 31, 2016
LICENSE.txt Update LICENSE.txt Jan 22, 2016
README.rst Updated dependencies in requirements.txt and also updated database se… Mar 5, 2014
alembic.ini Alembic migrations. Apr 20, 2013
requirements.txt RQ settings. Jun 1, 2013 RQ config and Alembic versioning in Jun 9, 2013 RQ config and Alembic versioning in Jun 9, 2013 Don't autocreate db tables. Jul 27, 2013
setup.cfg tests should cover all three lastuser blueprints Aug 20, 2013
test_requirements.txt Remove classmethod-based APIs Aug 27, 2013 Reorganized code into multiple blueprints. Mar 19, 2013



User management is a pain. There's no need to write new user management code for each new app to do basic things like logging in, managing the profile and verifying email addresses. Setup one Lastuser instance for all your apps and defer all user management to it. Use the API to integrate with your app.

This project is a work in progress.

Test deployment

Here is how you make a test deployment:

$ git clone
$ cd lastuser
$ cp instance/ instance/
$ open instance/ # Customize this file as needed
$ pip install -r requirements.txt
$ python

You may also want to setup the database with:

$ python db create

For development setup, you can also set the CACHE_TYPE to simple in instance/ or in instance/

#: Cache type
CACHE_TYPE = 'simple'