The ability for a user to belong to multiple sites.

For example, GET /sites/<uuid>/users/<id>/attributes/foo would read the JSON foo attribute for that user. PUT would set it.

Unit tests for all class models and modules.

Needed to create a test user, and was unable to. Tracking things here.

Noted this in the logs:

Sequel::Error - method firstname= doesn't exist:

A web form that helps site owners point-and-click their way to a user schema.

http://sequel.rubyforge.org/rdoc/files/doc/prepared_statements_rdoc.html

Ability to store end-user session data within Vellup. Haven't fleshed out the idea fully yet.

Instead of leaving the fields NULL, set them to an empty set ("{}") so it will at least be usable for schema validation.

At the moment, Vellup will tell you that it creates a user if you only provide an email and a password. However, it won't. At a skim, it looks like our problem is with the first migration:

      String      :firstname,     :size => 20, :null => false
      String      :lastname,      :size => 40, :null => false

I don't think we should require either of these fields, as email and password should be enough.

For example, for beta startups who want to grant accounts on a limited basis.

Integration tests for everything outlined in the API documentation. Ignore any web UI stuff for now as that's likely to be rewritten soon to use the API. Ideally we want to test all permutations of any particular endpoint using the mandatory and optional parameters, and testing failure conditions for the proper error codes.

Walk through the typical workflow: create a site, add a user, modify the user, modify the site, destroy the user and site, etc. If possible we should delete the test user/site from the database, as the destroy endpoint actually just disables and hides them.

Was adding auth to an app of mine, but could not find a way to do it easily. As it looks now, I have to provide a user id when I make a call to auth. In order to get that user id, I'm going to have to make a call to the api and find my user by email address.

I'd much rather do POST to something like https://vellup.herokuapp.com/sites/UUID/auth, passing that an email and a password. The result would ideally containing the user hash upon success.

Making notes.

Received the following upon signup:

Click the following link to complete your registration:
http://127.0.0.1:4567/confirm/[RANDOM UUID]

Allow site owners to determine password strength.

Such as address, twitter handle, etc. As part of this change, firstname/lastname should be moved out of the base schema and treated similarly.

Catch errors returned by json-schema and return them in an orderly fashion to the user.

errors = JSON::Validator.fully_validate(schema, data, :errors_as_objects => true)

[
  {
    :message=>"The property '#/a' of type String did not match the following type: integer in schema 03179a21-197e-5414-9611-e9f63e8324cd#",
    :schema=>#<URI::Generic:0x103a76198 URL:03179a21-197e-5414-9611-e9f63e8324cd#>,
    :failed_attribute=>"Type",
    :fragment=>"#/a"
  }
]