Results for migrate-well

Adds a rake task "db:migrate:well" that runs "rake db:migrate", "rake db:migrate:redo", "rake db:test:prepare" and "annotate". Options: "redo:false": without db:redo; "test:false": without db:test:prepare; "anno:false": without annotate.

Installs the protected_record gem and provides an interface for triaging ChangeRequest records

This gem is using for create custom field in dynamic form and add migration for the same and update schema as well.

Paraphraser, is a very simple gem. It adds a rake task that will drop, re-create and migrate a database (default is test) and will output the sql generated in the migration process. It will output the sql to screen as well as to a file ./migration.sql.

Nicely documented Push Notification gem for rails 3 applications, has generators for migrations and an initializer with configuration. It is well documented and tested.... compared to other shitty forks out there >_>

Use migrations and simple syntax to manage constraints in PostgreSQL DB.

This app extends active record to allow you to change the polymorphic type value in relationships. It also extends active record batching functions to be able to order records while batching. - As a bonus. the same 'split_batches' function is made available to Arrays It also adds optional auditing functions and password hashing functions, as well as migration helpers

SQrbL was created to help manage an extremely specific problem: managing SQL-based database conversions. In essence, SQrbL is a tool for managing multiple SQL queries using Ruby. SQrbL borrows some terminology and ideas from ActiveRecord's schema migrations, but where ActiveRecord manages changes to your database schema over time, SQrbL was written to manage the process of transforming your data from one schema to another. (Of course, you could use SQrbL for the former case as well -- just use it to write DDL queries -- but ActiveRecord has better tools for figuring out which migrations have already been applied.)

Migrate data from a legacy application to a new application, write scripts to import data from third-party applications, or convert data into the format your application expects--all in a flexible, declaritive syntax. Works with tabular data, such as CSV or database tables, with support for structured formats such as JSON as well.

The Promotion tool is designed to make it easy and quick to deploy an application into production. Originally built for use with OpenBSD, it can be used on an *nix system by adjusting a few paths (in config.rb). To deploy or install an application you just need to copy a few files into place, right? Well, the folders need to be there first of course, oh and the permissions need to be set, and I guess we need the right users set up before file ownerships can be set correctly, which means we need groups before that ... ok, so there is more to it than copying a few files. There are also system-wide settings that may need to be modified to support an application, such as environment variables in /etc/profile, /etc/sudoers, startup scripts in /etc/rc.conf.local, and /var/cron/tabs/* cron jobs. Promotion does not modify these sensitive files, but it does say how to change them. Promotion handles all of this based on an XML deployment descriptor for each application, allowing rapid, reliable redeployment with a single line command (promote). It also manages database schema migration with the evolve/devolve commands.

==== Topic Maps for Rails (rtm-rails) RTM-Rails is the Rails-Adapter for Ruby Topic Maps. It allows simple configuration of topicmaps in config/topicmaps.yml. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. You can use RTM as a complement data storage to ActiveRecord in your Rails apps. ==== Quickstart - existing Rails project jruby script/generate topicmaps Run the command above after installing rtm-rails. This will create * a minimal default configuration: config/topicmaps.yml and * a file with more examples and explanations config/topicmaps.example.yml * a file README.topicmaps.txt which contains more information how to use it and where to find more information * an initializer to load the topicmaps at startup * a rake task to migrate the topic maps backends in your rails application. ==== Quickstart - new Rails project For a new Rails application these are the complete initial steps: jruby -S rails my_topicmaps_app cd my_topicmaps_app jruby -S script/generate jdbc jruby -S script/generate topicmaps # The following lines are necessary because Rails does not have a template # for the H2 database and Ontopia does not support the Rails default SQLite3. sed -e "s/sqlite3/h2/" config/database.yml > config/database.yml.h2 mv config/database.yml.h2 config/database.yml # Prepare the database and then check if all is OK jruby -S rake topicmaps:migrate_backends jruby -S rake topicmaps:check ==== Usage inside the application When everything is fine, let's create our first topic: jruby -S script/console TM[:example].get!("http://example.org/my/first/topic") # and save the topic map TM[:example].commit Access the configured topic maps anywhere in your application like this: TM[:example] To retrieve all topics, you can do TM[:example].topics To retrieve a specific topic by its subject identifier: TM[:example].get("http://example.org/my/topic") Commit the changes to the database permanently: TM[:example].commit ... or abort the transaction: TM[:example].abort More information can be found on http://rtm.topicmapslab.de/ ==== Minimal configuration default: topicmaps: example: http://rtm.topicmapslab.de/example1/ The minimal configuration creates a single topic map, named :example with the locator given. This topic map will be persisted in the same database as your ActiveRecord connection if not specified otherwise. The default backend is OntopiaRDBMS (from the rtm-ontopia gem). A more complete configuration can be found in config/topicmaps.example.yml after running "jruby script/generate topicmaps". It also includes how to specifiy multiple connections to different data stores and so on. ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0

Contentful API wrapper library exposing an ActiveRecord-like interface

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.