rsence 2.0.0.7.pre → 2.0.0.8.pre

data/INSTALL.rdoc

@@ -1,6 +1,3 @@
-
-= NOTE: This installation manual isn't fully accurate at this time.
-
 = Installation
 
 If you already have a working ruby environment and know what to do, the easiest way is just:
@@ -25,23 +22,18 @@ This applies to all version of Mac OS X
 
 ==== 1.1.1. Mac OS X 10.4 and 10.5
 
-This step applies only to Mac OS X 10.4 Tiger and 10.5 Leopard
+This step applies only to Mac OS X 10.4 Tiger and 10.5 Leopard. The bundled ruby build of these versions of Mac OS X is somewhat broken.
 
-* Install these packages using Terminal:
+* Install the ruby and rb-rubygems packages using Terminal like this:
 
-  sudo port install ruby +thread_hooks
+  sudo port install ruby
   sudo port install rb-rubygems
 
 ==== 1.1.2 Mac OS X 10.6
 
-This step applies only to Mac OS X 10.6 Snow Leopard
-
-* Install this package using Terminal:
-
-  sudo port install sqlite3
-
+RSence works out-of-the box in Mac OS X 10.6 Snow Leopard.
 
-=== 1.2. Debian and Ubuntu GNU Linux
+=== 1.2. Debian and Ubuntu Linux
 
 This step applies only to Debian, Ubuntu and similar Linux distributions.
 
@@ -59,17 +51,17 @@ Windows compatibility has been officially tested on Windows XP SP3 and Windows 7
 * Download Ruby 1.8.7-p249 (RC2) from http://rubyinstaller.org/download.html
 * Run the downloaded exe to install ruby
   * In the installation and destination prompt, check these options:
-    * [x] Add Ruby executables to your PATH
-    * [x] Associate .rb and .rbw files with this Ruby installation
+    * Add Ruby executables to your PATH
+    * Associate .rb and .rbw files with this Ruby installation
 * Download and Install the Development Kit from http://rubyinstaller.org/download.html
   * Extract the included directories into the directory where you installed ruby.
     * It's C:\ruby by default.
 
 ==== 1.3.2. Install RSence
 * In the command prompt, run:
-  gem update --system
-  gem install rsence --pre
-  rsence help
+    gem update --system
+    gem install rsence --pre
+    rsence help
 
 ==== 1.3.3. Create RSence environment
 
@@ -78,18 +70,24 @@ Also, the 'my_project' project directory is just for illustration purposes.
 Use something else instead of those.
 
 * In the command prompt, run:
-  cd \my_projects
-  rsence initenv my_project
-* Answer the quetions
+    cd \my_projects
+    rsence initenv my_project
+* Answer the questions
 * In the command prompt, run:
-  rsence run my_project
+    rsence run my_project
 * Open your web browser in the address as configured.
   * If the address is 0.0.0.0, ether 127.0.0.1 instead.
+  * Using just defaults, the following url should work: http://127.0.0.1:8001/
 
 ==== 1.3.4. Windows limitations
-If you install the sqlite dll and the sqlite3-ruby gem, you'll gain persistent sessions and the "Warning: Session database is not available. Can't use persistent sessions" message will disappear when starting up rsence. It's not, however depended on in the default install, because it's not strictly required and makes the first installation much easier.
+If you install the sqlite dll and the sqlite3-ruby gem, you'll gain persistent sessions and this warning message will disappear:
+  Warning: Session database is not available. Can't use persistent sessions
+It's not, however, depended on in the default install, because it's not strictly required and makes the first installation much easier. Also, you can use any other database supported by Sequel instead of Sqlite.
+
 Backgrounding is not yet implemented, because POSIX signals are not fully implemented in windows and backgrounding requires some windows service hooks.
 
+However, if you run RSence under Cygwin, everything should work like on a unix machines.
+
 
 === 1.99. Other UNIX / Linux systems:
 
@@ -100,23 +98,17 @@ You'll have to figure out how to install the dependencies on your own, but gener
 * Ruby
   * Version 1.8.7 or newer
   * http://ruby-lang.org/
-* Rake
-  * Ruby replacement for make, needed for rubygems
-* Sqlite3
-  * Simple SQL library
 * RubyGems
   * Ruby package manager
-* A standard set of compilers and build tools
+* A standard set of compilers and build tools to build the gems with C extensions.
   * gcc, make etc.
 
 
 == 2. Ruby Dependencies
 
-The easiest way of installing a suggested set of these ruby gems is:
-  gem install rsence-deps
-
-This is equivalent to:
-  gem install rake highline rack mongrel soap4r rmagick json sequel sqlite3-ruby cssmin randgen jsmin_c jscompress html_min
+The 'rsence' gem depends on the dummy 'rsence-deps' gem, which depends on all essential dependencies of RSence.
+Optionally, you probably want at a database and a database adapter supported by Sequel: http://sequel.rubyforge.org/
+This not only enables SessionStorage (persistent sessions between RSence restarts), but some plugins written for RSence depend on at least Sqlite.
 
 === 2.1 Detailed list of ruby dependencies
 
@@ -140,7 +132,7 @@ This is equivalent to:
       * http://github.com/fauna/mongrel
     * *thin*
       * Quick
-      * Not as stable or reliable as mongrel
+      * Not as stable or reliable as mongrel (not at least yet)
       * http://code.macournoyer.com/thin/
     * *webrick*
       * No installation needed, part of the standard library
@@ -170,62 +162,103 @@ This is equivalent to:
       * Lightweight SQL library
     * Other database adapters compatible with sequel are fine. Just configure your setup accordingly.
 * *highline*
-  * Not needed, if you configure manually.
-* soap4r
-  * Optional, but required if you create SOAP services using the soap plugin
-  * Not recommended
+  * Used by the initenv command.
 * rmagick
-  * Optional, but suggested
+  * Optional, but suggested, because RSence has RMagick -savvy features, like serving RMagick objects using tickets that are rendered only when requested.
+  * Some plugins depend on it directly.
 
 
 == 3. Setting up RSence
 
-=== 3.1. Download RSence
-
-There are two main options: *release* and *development*. Choose one of these:
-* *release*:
-  * Latest stable release version.
-  * Strongly suggested for development and production use.
-  * Install as a gem:
-    gem install rsence
-  * *or* Manually download from:
-    * http://rsence.org/
-* *development*:
-  * The latest stable bleeding-edge version.
-  * Clone the GIT repository on github:
-    * http://github.com/rsence/rsence
+The primary installation method of RSence is via RubyGems.
 
-=== 3.2. Setting up
+To ensure your RubyGems is up-to-date, run:
+  sudo gem update --system
 
-==== 3.2.1. Start RSence in the development mode with logs printed to the standard output:
-  rsence run -df
+Even if RubyGems is up-to-date, ensure your installed gems are up-to-date, some of these are updated frequently. This will also update RSence release versions to the most recent version, if installed.
+  sudo gem update
+
+=== 3.1. Install RSence
 
-==== 3.2.2. Configuration
-When starting up RSence for the first time, a configuration wizard is run. Just press return on the questions to use the default configuration. The default option is upper case: pressing return at a "Y/n" prompt will select "Y"
+This will install RSence via RubyGems, the preferred method. All dependencies are installed too, except for the ones you already might have installed.
+  gem install rsence --pre
+
+Optionally, you might want to contribute to RSence development, just clone or fork the GIT repository on Github:
+  * http://github.com/rsence/rsence
 
+When installed, ensure it works by exploring the help of the 'rsence' command, like:
+  rsence
+  rsence help
+  rsence help version
+  rsence help run
+  rsence help initenv
+etc..
+
+=== 3.2. Setting up
+
+==== 3.2.1. Creating a RSence project environment
+
+To set up an environment for your RSence project, use the initenv command. In this example '/home/me/projects' is assumed as your project directory. Replace that with a path that matches your own environment. The RSence project directory must either be empty or will be created automatically.
+  rsence initenv /home/me/projects/my_first_rsence_project
+
+To see the options of the initenv command, use
+  rsence help initenv
+
+By default, initenv asks a few simple questions to write your configuration file. Just press enter, if you want to keep the suggested default options.
+
+The questions are:
+* Project Title
+  * This is the name of your project. It's displayed as the title of the RSence web page.
+* Session database connection string
+  * This is a database connection string for persistent RSence session storage. It allows keeping sessions valid even if RSence is restarted.
+  * You'll need the appropriate database adapter, most database engines are supported.
+  * The simplest (and default) database connection string is for a local Sqlite database.
+    * sqlite://db/ses.db
+    * This default example string is for a database named 'ses.db' to be created in the 'db' subdirectory of your project directory.
+  * The usual format is like any url, the following is for connecting to a mysql database named 'my_rsence_db' on the mysql server responding at 'localhost' on port '3306' using the username 'me' and password 'ins3cur3':
+    * mysql://me:ins3cur3@localhost:3306/my_rsence_db
+  * For more information, see:
+    * http://sequel.rubyforge.org/rdoc/files/doc/opening_databases_rdoc.html
+* HTTP Port
+  * This is the port RSence listens to. It may be any free and valid port number.
+* Interface TCP/IP address
+  * This is the address RSence binds to.
+  * '0.0.0.0' means RSence responds on all interface addresses configured on the computer.
+  * '127.0.0.1' means RSence responds only on localhost. For testing and development, use 127.0.01 instead of 'localhost' in the web browser url field, because cookies can't be set for 'localhost'.
+  * Any other IP address requires the same exact address to be configured on the computer RSence is running on.
+* URI Prefix
+  * This is by default the root directory, or /
+  * Change this to another 'virtual directory', if you are configuring several RSence instances on a virtual host served via a HTTP proxy, like mod_rewrite on apache.
+
+You may edit the conf/config.yaml at a later time to change these settings. The full list (and the defaults) are specified in the 'conf/default_conf.yaml' file in the installation directory of RSence.
+
+Any differences in your local configuration replace the default. If the configuration option type is an Array, the defaults are not replaced, the defaults are appended to. If your configuration only has partial items of a Hash defined, only those are applied to the default.
+
+==== 3.2.2. Start RSence in the development mode with logs printed to the standard output:
+
+The debug/development mode has the most verbose output and is the intended mode of RSence for development. Changes in your code are automatically (re)loaded and the javascript is not obfuscated or minimized in any way. Values also have human-readable id's.
+  cd /home/me/projects/my_first_rsence_project
+  rsence run -df
 
 ==== 3.3.3. Open a web browser
 * By default, the RSence listens on port 8001
 * To test it, open the address http://127.0.0.1:8001/
 * If everything works:
-  * Currently: An empty, white page without error messages is a sign of success.
-  * FIX 1:
-    * A welcome message is displayed
-    * Disables itself by touching a "disabled" file in its own directory.
-    * Implement the standard "runonce" plugin.
-  * FIX 2:
-    * A setup review / configuration plugin
-    * Implement the standard "setup" plugin.
+  * A welcome message is displayed
+  * Check the "Don't show again" checkbox and click the "Close" button to make the 'welcome' plugin uninstall itself.
+
+==== 3.3.4. Stop RSence
+Just press CTRL-C in the terminal, if RSence was started using the 'run' command.
 
-==== 3.3.4. Stop the server
-Just press CTRL-C in the terminal.
 
-==== 3.3.5. Manual configuration
-Edit the conf/config.yaml file. To see all available options at their default state, see conf/default_conf.yaml
+== 4. Modes of operation
 
+RSence supports two main modes of operation: in the foreground and in the background. Each have various options. Use the 'rsence help run' and 'rsence help start' commands to read more about them.
 
-== 4. Controlling the process
-For development purposes (and the only option on Microsoft Windows):
+
+=== 4.1. Starting RSence as a foreground process.
+
+The 'run' mode is well suited for development. Especially when combined with the -d and -f options.
 
 Starting in foreground mode:
   rsence run
@@ -238,59 +271,72 @@ Starting in foreground mode with debug and logging in foreground:
 
 Stopping in foreground mode: Press CTRL-C
 
-*NOTE: on Microsoft Windows:*
-* No backgrounding is supported, unless *run.rb* is configured as a Service.
 
-=== 4.1. Starting the server in background mode
-In the background mode, standard output and standard errors are logged in the var/log directory and the pidfile is written in the var/pid directory.
+=== 4.2. Starting RSence as a daemon (background mode).
+
+In the background mode, standard output and standard errors are logged in the 'log' directory of your project and the PID file is written in the 'run' directory. This mode of operation is best suited for production deployment and it's not available on Microsoft Windows, because full POSIX compliance is not available on Windows.
   rsence start
 
-=== 4.2. Stopping the server in background mode
+=== 4.2.1 Stopping RSence in background mode
   rsence stop
 
-=== 4.3. Checking the server status in background mode
+=== 4.2.2 Checking RSence status in background mode
   rsence status
 
-=== 4.4. Restarting the server in background mode
+=== 4.2.3 To store the RSence sessions into the session database while in background mode
+  rsence save
+
+The sessions are also stored when stopping and restarting RSence. Use the 'save' command regularly from a cron script or equivalent in a production environment.
+
+=== 4.3. Restarting RSence in background mode
   rsence restart
 
-=== 4.5. Re-setting the sessions
-This is needed only, if the session storage becomes corrupt or you just want to start with a clean set of sessions.
+=== 4.2.5. Re-setting the sessions
+This is needed only, if the session storage becomes corrupt in a development environment (changing value definitions and such). This invalidates all ongoing sessions.
 Just apply the --reset-sessions option after the run, start or restart command in the command prompt.
   rsence restart --reset-sessions
 
+The '-r' switch is equivalent to '--reset-sessions'
+
 *NOTE: All the sessions currently connected clients are invalidated and need to reload the page*
 
-=== 4.6. Running in development mode
+
+=== 4.4. Running in development mode
 Just apply the -d option after the *run*, *start* or *restart* command in the command prompt.
   rsence restart -d
 
-==== 4.6.1. What does development mode do?
-* Plugins are reloaded automatically in the background, if they are changed, disabled, added or removed.
+==== 4.4.1. What does development mode do?
+* Plugins are (re)loaded automatically in the background, if they are changed, disabled, added or removed.
+  * This is also enabled with the -a switch (--auto-update)
 * Javascript packages are automatically re-built, if they are changed.
-* Verbose logging
+  * This is also enabled with the -a switch (--auto-update)
+* Much more verbose logging
+* Code obfuscation / minimizing options are turned off.
 
-=== 4.7. Other command-line options
+=== 4.5. Other command-line options
 Just run this command to see the available options:
-  rsence help
+  rsence help <command>
+example:
+  rsence help run
 
-=== 4.8. Running RSence using rackup
+=== 4.6. Running RSence using rackup
   rackup conf/config.ru
 
-=== 4.9. Running RSence using unicorn
+=== 4.7. Running RSence using unicorn
   unicorn conf/config.ru -c conf/unicorn.conf
 
+
 == 5. Plugin Deployment
 
-If you followed, the previous steps, you are ready to deploy some software.
-* In development mode (see 4.6.), plugins are (re/un)loaded when:
+If you followed the previous steps, you are ready to deploy some software.
+* In development mode (see 4.4.), plugins are (re/un)loaded when:
   * Adding a new plugin into the plugins directory
   * Removing a plugin from the plugins directory
   * Disabling a plugin by creating a file or folder named "disabled" in the plugin's bundle directory
   * Enabling a plugin by removing a file or folder named "disabled" in the plugin's bundle directory
   * The plugin's ruby or yaml files are changed.
 
-* In production mode, a server restart is required (see 4.4.)
+* In production mode, a RSence restart is required (see 4.4.), unless running with the '-a' ('--auto-update') option enabled. Enabling it is a good idea for production environments where the code is updated frequently. It enables nearly zero downtime, if code updates are thoroughly tested before being deployed.
 
 * By default, the "plugins" directory in the "rsence" directory is the only plugin directory.
   * Edit the configuration file to enable other directories.
@@ -305,5 +351,14 @@ Move a plugin bundle out of the the "plugins" directory.
 
 === 5.3. Temporarily disabling a plugin
 Create an empty file named "disabled" in the plugin bundle to disable it.
-  touch rsence/plugins/legacy/disabled
+  touch plugins/legacy/disabled
+
+
+== 6. Getting more information
+
+* Explore http://rsence.org/
+* Join our chat room on IRC (IRCNet and FreeNode):
+  #rsence
+* Email a question to us:
+  info@rsence.org
 

data/README.rdoc

@@ -1,5 +1,5 @@
 
-= RSence 2.0.0.6.pre                                                       2010-??-??
+= RSence 2.0.0.x.pre                                                       2010-??-??
 
 http://rsence.org/
 
@@ -23,7 +23,7 @@ is the directory of your project) is:
 
   [dir]   project_directory   :: The directory of your project.
     [dir]   conf              :: The directory of config files.
-      [file]  config.yaml     :: The config file to load by defult.
+      [file]  config.yaml     :: The config file to load by default.
     [dir]   var               :: Directory containing various runtime files.
       [dir]  run              :: Directory containing PID files.
       [dir]  log              :: Directory containing log files.
@@ -46,16 +46,16 @@ The plugins directory contains the plugins installed in the project.
 
 Each command-line tool command takes a number of options, the path defaults to the current working directory.
 
-=== Running in foregrond
+=== Starting RSence in foreground
   rsence run /path/of/project
 
-=== Running in background
+=== Starting the RSence daemon
   rsence start /path/of/project
 
-=== Stopiing from background
+=== Stopping the RSence daemon
   rsence stop /path/of/project
 
-=== Restarting in background
+=== Restarting the RSence daemon
   rsence restart /path/of/project
 
 === Checking if project is running
@@ -69,7 +69,7 @@ Each command-line tool command takes a number of options, the path defaults to t
 === Getting detailed instructions of a command
   rsence help <command>
 
-eg:
+Example:
 
   rsence help run
 
@@ -78,7 +78,7 @@ For more detailed installation and usage instructions, read the INSTALL.rdoc doc
 
 === Licensing:
 * Free: *GPL*
-* Alternative licensing queries available via http://riassence.com/ and sales@riassence.com
+* Alternative licensing queries for commercial interests are available via http://riassence.com/ and sales@riassence.com
 
 === Community support:
 * Web: http://rsence.org/

data/VERSION

@@ -1 +1 @@
-2.0.0.7.pre
+2.0.0.8.pre

data/conf/default_strings.yaml

@@ -40,7 +40,7 @@
     # If the plugins rescan fails, display this:
     :valuemanager_sync_client_error:
       :title:  'SyncClientError'
-      :descr:  'The value syncronization to the client failed with error:'
+      :descr:  'The value synchronization to the client failed with error:'
       :uri:    '/'
     #
     # If the plugins rescan fails, display this:

data/conf/rsence_command_strings.yaml

@@ -251,7 +251,7 @@
   
       --port <number>         The port number the http server listens to.
   
-      --addr <ip address>     The IP address or netmask the http server listens to.
+      --addr <ip address>     The IP address or net mask the http server listens to.
                               '0.0.0.0' matches all interfaces.
                               '127.0.0.1' matches the local loopback interface.
   
@@ -287,7 +287,7 @@
   
      [d]  project_name       :  The name of your project.
        [d]  conf             :  The directory of config files.
-         [f]  config.yaml    :  The config file to load by defult.
+         [f]  config.yaml    :  The config file to load by default.
        [d]  db               :  Directory containing database files.
        [d]  log              :  Directory containing log files.
        [d]  plugins          :  Directory containing installed plugins.
@@ -312,7 +312,7 @@
   
       --port <number>         The port number the http server listens to.
   
-      --addr <ip address>     The IP address or netmask the http server listens to.
+      --addr <ip address>     The IP address or net mask the http server listens to.
                               '0.0.0.0' matches all interfaces.
                               '127.0.0.1' matches the local loopback interface.
                               Defaults to 0.0.0.0
@@ -389,7 +389,7 @@
     
       --port <number>         The port number the http server listens to.
     
-      --addr <ip address>     The IP address or netmask the http server listens to.
+      --addr <ip address>     The IP address or net mask the http server listens to.
   
   :save: |+
     usage: 'rsence save [options] [PATH]'
@@ -420,7 +420,7 @@
     backwards compatibility with software written for previous versions.
   
     The minor number designates minor changes in functionality, like minor or
-    moderate changes in functinality that usually don't impact backwards
+    moderate changes in functionality that usually don't impact backwards
     compatibilty of software written for a previous release with the same major
     version.
   

data/lib/plugins/pluginmanager.rb

@@ -228,15 +228,11 @@ module RSence
         :version => '0.0.0',
       
         # A brief description of the package (rdoc formatting supported)
-        :description => 'No Description given',
+        :description => 'No Description',
       
         # A flag (when false) prevents the plugin from automatically reload when changed.
         :reloadable => true,
       
-        # A flag (when false) enables automatic construction
-        # of the Plugin and Servlet classes contained.
-        :inits_self => false,
-      
         # System version requirement.
         :sys_version => '>= 1.0.0',
       
@@ -287,24 +283,20 @@ module RSence
         :src            => bundle_src
       } )
     
-      if bundle_info[:inits_self]
-        warn "Plugins can't init them self anymore. Please fix plugin: #{bundle_name.inspect}"
-      else
-        module_ns.constants.each do |module_const_name|
-          module_const = module_ns.const_get( module_const_name )
-          if module_const.class == Class
-            bundle_type = module_const.bundle_type
-            if [:Servlet, :Plugin, :GUIPlugin].include? bundle_type
-              bundle_inst = module_const.new( bundle_name, bundle_info, bundle_path, self )
-              bundle_inst.register( bundle_name ) if [ :Plugin, :GUIPlugin ].include?( bundle_type )
-              break
-            else
-              warn "Can't init class: #{module_const.to_s}"
-              break
-            end
+      module_ns.constants.each do |module_const_name|
+        module_const = module_ns.const_get( module_const_name )
+        if module_const.class == Class
+          bundle_type = module_const.bundle_type
+          if [:Servlet, :Plugin, :GUIPlugin].include? bundle_type
+            bundle_inst = module_const.new( bundle_name, bundle_info, bundle_path, self )
+            bundle_inst.register( bundle_name ) if [ :Plugin, :GUIPlugin ].include?( bundle_type )
+            break
           else
-            warn "module_const.class: #{module_const.class.inspect}"
+            warn "Can't init class: #{module_const.to_s}"
+            break
           end
+        else
+          warn "Invalid module_const.class: #{module_const.class.inspect}"
         end
       end
     end

data/plugins/client_pkg/info.yaml

@@ -16,10 +16,6 @@ description: |
 # A flag (when false) prevents the plugin from automatically reload when changed.
 reloadable: false
 
-# A flag (when false) enables automatic construction
-# of the Plugin and Servlet classes contained.
-inits_self: false
-
 # System version requirement.
 sys_version: '>= 2.0.0'
 

data/plugins/index_html/info.yaml

@@ -9,13 +9,6 @@ version: 2.0.0
 description: |
   This plugin serves the initial html page.
 
-# A flag (when false) prevents the plugin from automatically reload when changed.
-reloadable: true
-
-# A flag (when false) enables automatic construction
-# of the Plugin and Servlet classes contained.
-inits_self: false
-
 # System version requirement.
 sys_version: '>= 2.0.0'
 

data/plugins/main/info.yaml

@@ -7,14 +7,7 @@ version: 2.0.0
 
 # A brief description of the package (rdoc formatting supported)
 description: |
-  This manages communication between client and server.
-
-# A flag (when false) prevents the plugin from automatically reload when changed.
-reloadable: true
-
-# A flag (when false) enables automatic construction
-# of the Plugin and Servlet classes contained.
-inits_self: false
+  The main plugin manages the flow of communication between client and server.
 
 # System version requirement.
 sys_version: '>= 2.0.0'

data/plugins/ticket/info.yaml

@@ -0,0 +1,17 @@
+
+# The human-readable product name of the package
+title: Ticket services
+
+# The human-readable version of the package
+version: 2.0.0
+
+# A brief description of the package (rdoc formatting supported)
+description: |
+  This bundle provides various ticket services for serving files and file-like objects using disposable url's.
+
+# A flag (when false) prevents the plugin from automatically reload when changed.
+reloadable: false
+
+# System version requirement.
+sys_version: '>= 2.0.0'
+

data/setup/legacy/info.yaml

@@ -3,7 +3,7 @@
 title: Legacy Compatibility Plugin
 
 # The human-readable version of the package
-version: 2.0.0
+version: 1.0.0
 
 # A brief description of the package (rdoc formatting supported)
 description: |
@@ -13,10 +13,6 @@ description: |
 # A flag (when false) prevents the plugin from automatically reload when changed.
 reloadable: false
 
-# A flag (when false) enables automatic construction
-# of the Plugin and Servlet classes contained.
-inits_self: false
-
 # System version requirement.
 sys_version: '>= 2.0.0'
 

data/setup/welcome/info.yaml

@@ -3,7 +3,7 @@
 title: Welcome message
 
 # The human-readable version of the package
-version: 2.0.0
+version: 1.0.0
 
 # A brief description of the package (rdoc formatting supported)
 description: |
@@ -11,13 +11,6 @@ description: |
   environments, when the rsence initenv in executed.
   You may safely remove this plugin bundle.
 
-# A flag (when false) prevents the plugin from automatically reload when changed.
-reloadable: true
-
-# A flag (when false) enables automatic construction
-# of the Plugin and Servlet classes contained.
-inits_self: false
-
 # System version requirement.
 sys_version: '>= 2.0.0'
 

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification 
 name: rsence
 version: !ruby/object:Gem::Version 
-  hash: 961916136
+  hash: 961916116
   prerelease: true
   segments: 
   - 2
   - 0
   - 0
-  - 7
+  - 8
   - pre
-  version: 2.0.0.7.pre
+  version: 2.0.0.8.pre
 platform: ruby
 authors: 
 - Riassence Inc.
@@ -17,7 +17,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-05-18 00:00:00 +03:00
+date: 2010-05-19 00:00:00 +03:00
 default_executable: rsence
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -98,6 +98,7 @@ files:
 - plugins/main/js/riassence_ns.js
 - plugins/main/main.rb
 - plugins/main/values.yaml
+- plugins/ticket/info.yaml
 - plugins/ticket/lib/common.rb
 - plugins/ticket/lib/favicon.rb
 - plugins/ticket/lib/file.rb