Added project files

Author: dbrgn

.gitignore

@@ -0,0 +1,4 @@
+*.swp
+*.lock
+target/
+*.bk

.travis.yml

@@ -0,0 +1,16 @@
+language: rust
+sudo: false
+rust:
+  - stable
+  - beta
+  - nightly
+services:
+  - redis-server
+notifications:
+  irc:
+    channels:
+      - "chat.freenode.net#coredump"
+    on_success: change
+    on_failure: always
+    use_notice: true
+    skip_join: true

AUTHORS.md

@@ -0,0 +1,4 @@
+# Contributors
+
+- Danilo Bargen (@dbrgn)
+- Raphael Nestler (@rnestler)

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributors Guideline
+
+We're very happy if people contribute to our projects! To keep quality high,
+please adhere to the following standards though:
+
+- **Always create a fork or branch** if you develop a new feature or fix. Then
+  create a pull request against `master` to get the changes integrated.
+- **Run the tests** (`cargo test`) before committing and pushing your changes.
+- **Write meaningful commit messages**: First line of your commit message should be
+  a very short summary in the imperative mood without any punctuation symbols
+  (ideally 50 characters or less). After the first line of the commit message,
+  add a blank line and then a more detailed explanation (when relevant).
+  [This](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) is
+  a nice blog post concerning git commit messages.
+- **Keep your commit history clean**. If there are typo commits that should be squashed
+  or if you want to re-order commits, please use `git rebase -i` or `git commit --amend`
+  to clean up your commit history.
+
+If you're a member of the development team (having push access to the repository):
+
+- Create a pull request, then wait for another member of the team to review
+  your changes. Only merge your PR if you got a "good to merge" comment.
+- Don't merge the pull requests of other members of the development team.
+  Instead, let them know that you think their contribution is good to merge.
+
+If you're an outside contributor:
+
+- Simply create a pull request and wait for a team member to merge it.

LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2014-2015 coredump Rapperswil
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

README.md

@@ -0,0 +1,41 @@
+# Rust Space API Implementation
+
+[![Build Status](https://travis-ci.org/coredump-ch/spaceapi-server-rs.svg?branch=master)](https://travis-ci.org/coredump-ch/spaceapi-server-rs)
+
+This is a library that allows an easy implementation of a
+[SpaceAPI](http://spaceapi.net/) v0.13 server in Rust.
+
+Space API Reference: http://spaceapi.net/documentation
+
+
+## Usage
+
+TODO
+
+
+## Datastores
+
+### Redis
+
+To use the redis storage start the redis server:
+
+    $ redis-server
+
+(...or start it using your favorite init daemon.)
+
+You can access the database with the `redis-cli` tool:
+
+    % redis-cli
+    127.0.0.1:6379> SET people_present 1
+    OK
+    127.0.0.1:6379> GET people_present
+    "1"
+    127.0.0.1:6379> KEYS *
+    1) "people_present"
+
+The values depend on your sensors configuration.
+
+
+## Docs
+
+You can build docs with `make docs`. Find them in the `target/doc/` directory.

rustfmt.toml

@@ -0,0 +1 @@
+max_width = 110