Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
User management in each new app is a pain. This is the last time you should be doing it
branch: master
Failed to load latest commit information.
alembic Longer external usernames
instance Added sms config to sample settings
lastuser_core Longer external usernames
lastuser_oauth Widget attrs in forms
lastuser_ui Widget attrs in forms
lastuserapp Enable app-wide CSRF
tests Fix test
.gitignore PEP8 compliance
.travis.yml Fix Travis.
CHANGES.rst Refactoring complete. Now a multi-file app.
LICENSE.txt Update copyright. Refactoring complete. Now a multi-file app.
README.rst Updated dependencies in requirements.txt and also updated database se…
alembic.ini Alembic migrations.
config.rb Reorganized code into multiple blueprints. i18n and string type consistency
requirements.txt Use of load_only in… RQ settings. RQ config and Alembic versioning in RQ config and Alembic versioning in Don't autocreate db tables.
setup.cfg tests should cover all three lastuser blueprints Make models available in shell. i18n and string type consistency
test_requirements.txt Remove classmethod-based APIs



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'
Something went wrong with that request. Please try again.