Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/pluf/user

A pluf module to manage user profiles and user accounts
https://github.com/pluf/user

Last synced: about 23 hours ago
JSON representation

A pluf module to manage user profiles and user accounts

Awesome Lists containing this project

README

        

# User

[![Build Status](https://travis-ci.com/pluf/user.svg?branch=master)](https://travis-ci.com/pluf/user)
[![codecov](https://codecov.io/gh/pluf/user/branch/master/graph/badge.svg)](https://codecov.io/gh/pluf/user)
[![Coverage Status](https://coveralls.io/repos/github/pluf/user/badge.svg)](https://coveralls.io/github/pluf/user)
[![Maintainability](https://api.codeclimate.com/v1/badges/9e1457dbf2f0bcc8b953/maintainability)](https://codeclimate.com/github/pluf/user/maintainability)
[![Test Coverage](https://api.codeclimate.com/v1/badges/9e1457dbf2f0bcc8b953/test_coverage)](https://codeclimate.com/github/pluf/user/test_coverage)

این پروژه یک ماژول برای سرورهای pluf است که امکانات مدیریت پروفایل‌ها و حساب‌های کاربری را فراهم می‌کند.

این ماژول به ماژول‌های زیر وابستگی دارد:

- pluf/user
- pluf/collection

از نکات مهم این ماژول این است که ساختار پروفایل ثابت نیست و می‌تواند در سیستم‌های مختلف متفاوت باشد
پروفایل در اینجا به صورت یک نگاشت کلید-مقدار است که هر زوج کلید-مقداری را می‌توان در آن ذخیره کرد.

## Update from V3

### DB

#### Copy table `user` to `user_accounts` and `user_profiles`

In `user_accounts` keep following attributes:

- id
- login
- date_joined
- last_login
- active

Add the following:

- deleted

#### add `user_emails` table

#### rename `user_groups`

#### rename `user_messages`

## Contributing

If you would like to contribute to Pluf, please read the README and CONTRIBUTING documents.

The most important guidelines are described as follows:

>All code contributions - including those of people having commit access - must go through a pull request and approved by a core developer before being merged. This is to ensure proper review of all the code.

Fork the project, create a feature branch, and send us a pull request.

To ensure a consistent code base, you should make sure the code follows the PSR-2 Coding Standards.