Skip to content
pascalBokBok edited this page Feb 8, 2014 · 15 revisions

Welcome to the OpenSourceMemberManager wiki!

System architecture

Philosophy

Simple is elegant. Minimalistic.

We have 3 parts

  1. Backend for storing and loading membership information
  2. Frontend for managing memberships
  3. Database schema

First version - released.

Features:

  • Backend
    • Initialization, insert, delete, list members using sqlite database store
    • Encryption of database file.
  • Frontend
    • Basic HTML with AJAX handling communication with API.
    • the API acts as a bridge to the backend.
  • Database schema
    • Basic members: id, name, email-address, last-enrollment

Chosen not to do:

  • No administrator. Right now open to all unless constrained with htaccess.

Second version

  • Add authorization to mix
    • administrator users,
    • deny direct public access to db-file (e.g. .htaccess)
  • Database tables defined in JSON format.
    • DB can created from it
    • Frontend can know more about how to act on each data-field

#Other open source solutions