User Management

This widely-used plugin provides a foundation for securely managing user.

Make avaiable to your users for login with Devise or Facebook, and manage them and your admins. Each admin is related to roles with Rolify, and manages authorization with CanCan.

This widely-used plugin provides a foundation for securely managing user.

Schools augments user's profiles with an associated school, along with interfaces for adding new schools at runtime. Administrators can manage schools and modify learner's schools.

This widely-used plugin provides a foundation for securely managing user.

[Messente](https://messente.com) is a global provider of messaging and user verification services. * Send and receive SMS, Viber, WhatsApp and Telegram messages. * Manage contacts and groups. * Fetch detailed info about phone numbers. * Blacklist phone numbers to make sure you're not sending any unwanted messages. Messente builds [tools](https://messente.com/documentation) to help organizations connect their services to people anywhere in the world.

Simple account management based on tiny_core_users

AnNCR-SNP integrates data from various sources, allowing the user to investigate the potential effects of variants in non-coding regions of the human genome. AnNCR-SNP consists of a database containing data on all non-coding elements and two main programs: manager and finder. The manager program is responsible for creating the local data-base, and the finder program receives the user queries in order to search in the local database and retrieve information. The user can find information about various regu-latory elements, such as TFBs, open chromatin, histone modification and methyla-tion sites, information about SNPs from dbSNP and gene information from RefSeq.

motr-cargo is a collection of Motr mods that add functionality for managing and delivering user managed/generated content

A warden/sinatra mini-app providing authentication and user management for any rack-based framework.

A thoroughly civilized CMS for Rails apps which deal with user generated content. Chunks is a Rails engine providing out-of-the-box management and rendering for pages composed of self-contained chunks of content. Each Chunk is comprised of an edit view, a public view, and a view model which will be updated, validated, and invoked by the ChunksPublicController if server-side interaction is required. The Chunks controller quickly delegates all responsibility for logic and page flow to an individual Chunk view model while the framework gets out of the way altogether, allowing for extremely easy extension and migration onto or off the Chunks framework. Documentation and extensions available at http://www.chunkscms.com.

Creates a new class, Editable_Content, which manages content which can be saved in a database and edited by a user.

Giticious is a simple Git with user management

Manage authorization restrictions on Ruby on Rails. Ideal for controlling actions of 2 or 3 types of users.

Rails 3 engine for managing an app's assets, users, pages, blog, SEO and Social Media Integration

Paradeiser is a command-line tool for the Pomodoro Technique. It keeps track of the current pomodoro and assists the user in managing active and past pomodori as well as breaks. Status commands and reports are provided to get insights.

Use this gem to manage several features of the Telebyte eletronic timeclocks, like report creation, user management, configuration etc.

Cloud Run deploys and manages user provided container images that scale automatically based on incoming requests.

Client-side library for manipulating RESTful resources provided by Personas, a Rails + Backbone user managment service

This admin_template plugin provides a foundation for securely managing user.

This web interface provides various administrative tools for the leap platform through plugins. Currently it manages user accounts and certificates.

BackendFu takes the hassle out of user management.

Mountable engine with user management and authenthication in your API.

An enterprise-grade Database is provided as a Service (DBaaS) solution that can be managed through a browser-based "Data Center Designer" (DCD) tool or via an easy to use API. The API allows you to create additional PostgreSQL database clusters or modify existing ones. It is designed to allow users to leverage the same power and flexibility found within the DCD visual tool. Both tools are consistent with their concepts and lend well to making the experience smooth and intuitive.

user manage system with rails

Ruby on Rails 7 Authentication and User Management Engine using Devise with a nice-looking dashboard, admin panel and login views to get you going fast on your next project.

Management your mysql users. You can do that by simple settings written by yaml

User management for aerogel

== README.md: #ScheduledResource This gem is for displaying how things are used over time -- a schedule for a set of "resources". You can configure the elements of the schedule and there are utilities and protocols to connect them: - Configuration (specification and management), - Query interfaces (a REST-like API and internal protocols to query the models), and - A basic Rails controller implementation. We have a way to configure the schedule, internal methods to generate the data, and a way to retrieve data from the client. However this gem is largely view-framework agnostic. We could use a variety of client-side packages or even more traditional Rails view templates to generate HTML. In any case, to get a good feel in a display like this we need some client-side code. The gem includes client-side modules to: - Manage <b>time and display geometries</b> with "infinite" scroll along the time axis. - <b>Format display cells</b> in ways specific to the resource models. - <b>Update text justification</b> as the display is scrolled horizontally. ## Configuration A **scheduled resource** is something that can be used for one thing at a time. So if "Rocky & Bullwinkle" is on channel 3 from 10am to 11am on Saturday, then 'channel 3' is the <u>resource</u> and that showing of the episode is a <u>resource-use</u> block. Resources and use-blocks are typically Rails models. Each resource and its use-blocks get one row in the display. That row has a label to the left with some timespan visible on the rest of the row. Something else you would expect see in a schedule would be headers and labels -- perhaps one row with the date and another row with the hour. Headers and labels also fit the model of resources and use-blocks. Basic timezone-aware classes (ZTime*) for those are included in this gem. ### Config File The schedule configuration comes from <tt>config/resource_schedule.yml</tt> which has three top-level sections: - ResourceKinds: A hash where the key is a Resource and the value is a UseBlock. (Both are class names), - Resources: A list where each item is a Resource Class followed by one or more resource ids, and - visibleTime: The visible timespan of the schedule in seconds. The example file <tt>config/resource_schedule.yml</tt> (installed when you run <tt>schedulize</tt>) should be enough to display a two-row schedule with just the date above and the hour below. Of course you can monkey-patch or subclass these classes for your own needs. ### The schedule API The 'schedule' endpoint uses parameters <tt>t1</tt> and <tt>t2</tt> to specify a time interval for the request. A third parameter <tt>inc</tt> allows an initial time window to be expanded without repeating blocks that span those boundaries. The time parameters _plus the configured resources_ define the data to be returned. ### More About Configuration Management The <b>ScheduledResource</b> class manages resource and use-block class names, id's and labels for a schedule according to the configuration file. A ScheduledResource instance ties together: 1. A resource class (eg TvStation), 2. An id (a channel number in this example), and 3. Strings and other assets that will go into the DOM. The id is used to - select a resource _instance_ and - select instances of the _resource use block_ class (eg Program instances). The id _could_ be a database id but more often is something a little more suited to human use in the configuration. In any case it is used by model class method <tt>(resource_use_block_class).get_all_blocks()</tt> to select the right use-blocks for the resource. A resource class name and id are are joined with a '_' to form a tag that also serves as an id for the DOM. Once the configuration yaml is loaded that data is maintained in the session structure. Of course having a single configuration file limits the application's usefulness. A more general approach would be to have a user model with login and configuration would be associated with the user. ## Installation Add this line to your application's Gemfile: ```ruby gem 'scheduled_resource' ``` And then execute: $ bundle Or install it yourself as: $ gem install scheduled_resource Then from your application's root execute: $ schedulize . This will install a few image placeholders, client-side modules and a stylesheet under <tt>vendor/assets</tt>, an example configuration in <tt>config/resource_schedule.yml</tt> and an example controller in <tt>app/controllers/schedule_controller.rb</tt>. Also, if you use $ bundle show scheduled_resource to locate the installed source you can browse example classes <tt>lib/z_time_*.rb</tt> and the controller helper methods in <tt>lib/scheduled_resource/helper.rb</tt> ## Testing This gem also provides for a basic test application using angularjs to display a minimal but functional schedule showing just the day and hour headers in two different timezones (US Pacific and Eastern). Proceed as follows, starting with a fresh Rails app: $ rails new test_sr As above, add the gem to the Gemfile, then $ cd test_sr $ bundle $ schedulize . Add lines such as these to <tt>config/routes.rb</tt> get "/schedule/index" => "schedule#index" get "/schedule" => "schedule#schedule" Copy / merge these files from the gem source into the test app: $SR_SRC/app/views/layouts/application.html.erb $SR_SRC/app/views/schedule/index.html.erb $SR_SRC/app/assets/javascripts/{angular.js,script.js,controllers.js} and add <tt>//= require angular</tt> to application.js just below the entries for <tt>jquery</tt>. After you run the server and browse to http://0.0.0.0:3000/schedule/index you should see the four time-header rows specified by the sample config file. ## More Examples A better place to see the use of this gem is at [tv4](https://github.com/emeyekayee/tv4). Specifically, models <tt>app/models/event.rb</tt> and <tt>app/models/station.rb</tt> give better examples of implementing the ScheduledResource protocol and adapting to a db schema organized along somewhat different lines. ## Contributing 1. Fork it ( https://github.com/emeyekayee/scheduled_resource/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request

Turnitin Core API (TCA) provides direct API access to the core functionality provided by Turnitin. TCA supports file submission, similarity report generation, group management, and visualization of report matches via Cloud Viewer or PDF download. Below is the full flow to successfully set up an integration scope, an API Key, and make calls to TCA. Integration Scope and API Key management is done via the Admin Console UI by logging in as an admin user. For more details, go to our [developer portal documentation page](https://developers.turnitin.com/docs). ## Integration Scope and API Key Management TCA API calls must provide an API Key for authentication, so you must first have at least one integration scope associated with at least one API Key to use TCA. ### Admin Console UI First, login to Admin Console UI as an *Admin* user with permission to create Integration Scopes, under a tenant that is licensed to use the TCA product Integration Scopes (you can create a new one, or add keys to existing) * Click `Integrations` in the side bar --> `+ Add Integration` at top the top of the page --> Enter a name --> `Add` Button API Keys * Click `Integrations` in the side bar --> `Create API Key` Button next to a given Integration Scope --> Enter a name --> click `Create and View button` * Copy/Save the key manually or click save to clipboard button to copy it (this is the only time it will show) ## TCA Flow * Register a webhook * Create a submission * Upload a file for the submission * Wait for the submission upload to process * If you registered a webhook, a callback will be sent to it when upload is complete * The status of the *submission* will also update to `COMPLETE` * Request a Similarity Report * Wait for similarity report to process * If you registered a webhook, a callback will be sent to it when report is complete * The status of the *report* will also be updated to `COMPLETE` * Request a URL with parameters to view the Similarity Report

Ruby on Rails 7 Authentication and User Management Engine using Auth0 with a nice-looking dashboard, admin panel and login views to get you going fast on your next project.

A gem which manages printing between barcodeWeb and the user's machine.

Management tool for unix users. Manually edits `/etc/passwd`, `/etc/shadow` and `/etc/groups`.

Once installed, the gem will add forem related fields to the Spree::User admin form so you can manage Forem users from the Spree Admin panel (Users)

dsu is ruby gem that enables anyone practicing Agile methodology to record, keep track of, and manage their daily standup (DSU) activities. * dsu uses no network connections whatsoever. * dsu stores all of its data locally, in .json files. * dsu is a simple (but powerful) command-line tool for users who love to work within the terminal. * dsu versioning follows the semantic versioning standard (MAJOR.MINOR.PATCH).

A manager for unix users and group to control /etc/passwd and /etc/group

Creates, terminates, and monitors Amazon EC2 instances. Creates more instance to meet increased demand, and terminates them when they are no longer needed. Any number of pools of instances may be managed. Provides periodic status reports. Three policies are provided: a fixed size pool policy, a job-oriented batch policy, and a resource-limited stateful policy. The user can define additional policies. To get started, see http://code.google.com/p/cloudmaster/wiki/Introduction

Claudius is an easy-to-use domain specific language for cloud experiments. It has been designed to speed up process of building distributed experiments and highly reduce time of remote machines configuration. To avoid vendor lock-in, Claudius was build on top of fog.io library, which enables flexible and powerful way to manage machine instances at various cloud providers. Remote commands execution is based on SSH protocol (SSH-2). DLS allow users to generate readable execution graph, which is extremely useful for experiment flow verification and help avoid wasting your money.

Keep track of your devices. Features: - User registration/login/validation - User levels (normal/admin) - Checkout devices - Return devices - Assign devices to someone (Admin only) - Validate a user (Admin only) - Search devices - Keep track of number of times devices used - Manage OS versions - Send reminders to someone who has had a device checked out for a long time - Password reset

blinkbox ruby user management api

CanCamel allows to manage access levels with all the power of cancan style (saving semantics). It means, that you can use `can?` method anywhere you want to check privileges of a selected user to access something in some way. See readme file at https://github.com/JelF/can_camel/blob/master/README.md to learn more

Keep track of your devices. Features: - User registration/login/validation - User levels (normal/admin) - Checkout devices - Return devices - Assign devices to someone (Admin only) - Validate a user (Admin only) - Search devices - Keep track of number of times devices used - Manage OS versions - Send reminders when devices have been out for period of time - Password reset

Ruby enVironment Manager - Text-based User Interface

Fickle lets you turn features on and off at will in your rails app using a web interface. It also lets you manage features on a model-by-model basis (maybe users?)

Svnbranch is a program that can assist with managing Subversion branches. Svnbranch allows users to easily create new software branches, and merge in changes from a different repository branch. Using branches in software development is a key concept in managing large projects. Indeed, the GIT source code management package provides an incredibly easy way to manage branches, and branch use is greatly encouraged by several large FOSS projects, for instance the Linux kernel. Svnbranch attempts to offer the same level of user-friendliness to Subversion users. Subversion does branching very well, but its syntax escapes many, or is downright long and tedious. Instead of typing in long, error-prone svn commands, Svnbranch abstracts one layer above the Subversion command line utility providing simple command syntax for common use cases. The result is that with more powerful tools, developers may take advantage of the benefits of branched development practices.

Manage user roles. Each user's role is stored as a bit in an integer column of database. Also provides user ability to have one role and some roles.

Pipet is a package manager for bioinformatics databases that allows users to easily retrieve databases from their sources using the command line. Pipet also checks for database integrity via checksum

Simple reusable user management with generator based on authlogic

The Ruby library for the Elastic Email REST API. This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. To start using this API, you will need your Access Token. Remember to keep it safe.

Makes it easy for RoR backend to interact with front-end and external services to manage User lifecycle, e.g., signup, login, etc.