<commit_before>SRAS -- Simple Ruby Asset Server... for OpenSimulator
==========================================================

Features
--------

 * Asset de-duplication
 * Compressed asset storage on disk
 * Ability to disable serving of specific assets without deleting


Install
-------

The packages of Ruby shipping with Ubuntu don't include built-in zlib
support.  I prefer using RVM [ http://rvm.beginrescueend.com/ ]
anyway.

Built & testing with Ruby v1.9.2.

Install gems: ::

    $ gem install bundler
    $ cd /path/to/sras
    $ bundle install

Tested with Thin, but should also work with Passenger.


Running
-------

Configure: ::

    $ cp config/config.yml.example config/config.yml
    $ # edit config/config.yml to your liking
    $ rake db:create

Then just: ::

    $ bin/sras start

to start a single instance.  In a production environment you would
likely want to run several instances behind a reverse proxy like
Nginx.

To see additional options: ::

    $ bin/sras --help
<commit_msg>update README.rst<commit_after>SRAS -- Simple Ruby Asset Server... for OpenSimulator
==========================================================

Features
--------

 * Asset de-duplication
 * Compressed asset storage on disk
 * Ability to disable serving of specific assets without deleting


Install
-------

The packages of Ruby shipping with Ubuntu don't include built-in zlib
support.  I prefer using RVM [ http://rvm.beginrescueend.com/ ]
anyway.

Built & testing with Ruby v1.9.2.

Install gems: ::

    $ gem install bundler
    $ cd /path/to/sras
    $ bundle install

Tested with Thin, but should also work with Passenger.


Running
-------

Configure: ::

    $ cp config/config.yml.example config/config.yml
    $ # edit config/config.yml to your liking
    $ rake db:create

Then just: ::

    $ bin/sras start

to start a single instance.  In a production environment you would
likely want to run several instances behind a reverse proxy like
Nginx.

To see additional options: ::

    $ bin/sras --help


Testing
-------

To test asset creation: ::

    $ curl -d @test/test.asset -X POST -w '%{http_code}\n' \
        http://yourserver.example.com:8003/assets/

You should get a 200 HTTP response, have an entry in your assets
table, and have a file contain the asset data on disk.

To test retrieval of that asset: ::

   $ curl -X GET \
        http://yourserver.example.com:8003/assets/0193663d-44e4-4e6e-9a1c-8dd2febc5fc5/data 


Mailing List
------------

For SRAS-related announcements and discussion feel free to join the
low-volume mailing list.  To join the list send an email to
<EMAIL> with the following body (no subject required):

    subscribe sras-l

Mailing list members can email the list via <EMAIL>

List archives can be found at http://lists.coyled.com/sras-l/archives/
{'fraction_non_alphanumeric': 0.13600852272727273, 'fraction_numerical': 0.012428977272727272, 'mean_word_length': 3.035816618911175, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '554023', 'n_tokens_mistral': 872, 'n_tokens_neox': 801, 'n_words': 319}