Results for connectivity-map

==== 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

This gem provides a class with methods which map directly to the SQL stored procedure APIs provided by pglogical. It also provides a way to mix these methods directly into the ActiveRecord connection object.

Display progress bars with percentage, ETA, and throughput, or spinners for indeterminate tasks. Supports block-based usage, enumerable iteration with each/map, background auto-spinning, multi-bar tracking, and auto-disables rendering when not connected to a terminal.

Elasticshell provides a command-line shell 'es' for connecting to and querying an Elasticsearch database. The shell will tab-complete Elasticsearch API commands and index/mapping names.

Wrapper class for a Vagrant VM, providing access to testing predicates, such as port map information, process data, ssh connections, and more.

Gridmap makes tile based maps easy. It offers 2 new classes - a gridmap and a tile. It takes care of drawing tiles with connected textures (e.g. walls).

==== Ruby Topic Maps (RTM) RTM is a Topic Maps engine written in Ruby. See http://rtm.topicmapslab.de/ for instructions. Several backends and extensions are available as separate gems. ==== 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. ==== Quickstart require 'rtm' connection = RTM.connect # uses the default Ontopia in-memory backend topic_map = connection.create "http://example.org/my_topic_map/" some_topic = topicmap.get!("identifier_of_the_topic") some_topic["-"] = "default name for the topic" topic_map.to_xtm("my_xtm_file.xtm") ==== 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/. ==== Backends * rtm-ontopia: JRuby only, recommended, uses Ontopia: http://code.google.com/p/ontopia/ * rtm-tinytim: JRuby only, uses TinyTiM: http://tinytim.sourceforge.net/ * rtm-activerecord: uses a custom ActiveRecord schema ==== Extensions * rtm-tmql: Adds support for the Topic Maps Query Language (TMQL), http://isotopicmaps.org/tmql/ * rtm-tmcl: Adds support for the Topic Maps Constraint Language (TMCL), http://isotopicmaps.org/tmcl/ ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0

Redis::Directory assumes a Redis installation running on a default port and database 0 that will contain connection information for various other Redis databases. For example, if you were using a Redis database to store the content of cached pages, and this was running on a cluster of two Redis instances, with multiple applications connecting partitioned by database, then your connection might look like this: require "redis" require "redis/distributed" # The ACME Corp database is #27 cache = Redis::Distributed.new "redis://redis.example:4400/27", "redis://redis.example:4401/27" Redis::Directory uses a centralized Redis database to store the connection information so you don't have to remember "magic numbers" for each client/database mapping, and can easily update port-numbers/hostnames, cluster-members as necessary. The same connection with Redis::Directory would look like this: require "redis_directory" cache = Redis::Directory.new("redis.example").connect("cache", "acme")

Auto-syncs records in client-side JS (through a Model DSL) from changes (updates/destroy) in the backend Rails server through ActionCable. Also supports streaming newly created records to client-side JS. Supports lost connection restreaming for both new records (create), and record-changes (updates/destroy). Auto-updates DOM elements mapped to a record attribute, from changes (updates/destroy).

The Internet Communications Engine (Ice) provides a robust, proven platform for developing mission-critical networked applications with minimal effort. Let Ice handle all of the low-level details such as network connections, serialization, and concurrency so that you can focus on your application logic. This package includes the Ice extension for Ruby, the standard Slice definition files, and the Slice-to-Ruby compiler. You will need to install a full Ice distribution if you want to use other Ice language mappings, or Ice services such as IceGrid, IceStorm and Glacier2. We provide extensive online documentation for Ice, the Ruby extension, and the other Ice language mappings and servicespec. Join us on our user forums if you have questions about Ice.

Graffiti is an RDF store based on dynamic translation of RDF queries into SQL. Graffiti allows one to map any relational database schema into RDF semantics and vice versa, to store any RDF data in a relational database. Graffiti uses Sequel to connect to database backend and provides a DBI-like interface to run RDF queries in Squish query language from Ruby applications.

activeadmin-oidc plugs generic OpenID Connect single sign-on into ActiveAdmin. It builds on Devise + omniauth_openid_connect and adds JIT user provisioning, role mapping from provider claims via a host-owned on_login hook, and a single install generator that wires everything up.

No description provided.

No description provided.

No description provided.