tsurezure 0.0.31 → 0.0.32

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a3f470685236ef86ac858933ef4c913a99f21a4e0d42572971518781056c68f1
-  data.tar.gz: b6aede8db5d91dc1be40ddca3fc5011e1494084eb5e38f7df30edd8a426a316d
+  metadata.gz: 6cd3e3004d9cab6a40d5eb0c2e0e522ef3423f04e4ea7a8d476e2599352bf3fd
+  data.tar.gz: 7a7142acec9a8fb170e15eaca64e18a3a6ddcd319b63978cefb787105a2d38b4
 SHA512:
-  metadata.gz: 73dc499f770f090d7c5ad90ebfd3cf59922c105e84bb4a65713694b0d802c79ecc1e1a36191de3dd6e90984df689319bc4d3cdfb9e89de3e87891448bf543c91
-  data.tar.gz: 4e9f7c5e21fa6b3f9d422c21026a9bf07a1c02269fad26c1a16f36f155bb8a17f48c045a22b637fdd3ed31e6f0dde8b4b70d11449c0ff6b0fc7a0eadd8cd091f
+  metadata.gz: a3b55a314479b66ca54718a3f739ee574edf8cea0b02b59645c2f5f84063a59da7a15549130913f71bc8ae0ec5503fda63ee8b24d12727dd5229212b022501e8
+  data.tar.gz: ea4dae6aef7898ab8e6decab4720a4c825f1a124295ea8751225a85c70d513605b3a824d5403354ee504ba40b1d33157a6757c7808d479b4496d5e2062c6b5e4

data/readme.md

@@ -1,150 +1,152 @@
-# tsurezure
-
-this is a simple web server framework written in ruby. mainly made as a way for me to quickly put together rest apis in my favorite language.
-
-it can be used in a very similar manner to the javascript framework express.
-
-* * *
-
-## usage
-
-### installing (from rubygems)
-
-just run `gem install tsurezure` and you'll have whatever the latest version is that I've put up.
-
-### installing (from source):
-
-requires:
-
--   ruby
--   nodejs + nodemon (**only** for hot reloading server in development mode, not necessarily required)
-
-after cloning this repo, from the root project directory, just run `rake start` to start in production mode, or `rake dev` to run in development mode, which adds hot reloading with nodemon. gem dependencies will install automatically.
-
-to build the gem: run `gem build tsurezure.gemspec`. then, install using `gem install tsurezure-version-number`. `version-number` is whatever version is installed based on the `.gemspec` file.
-
-### commands
-
--   `rake install` will install dependencies
--   `rake check_deps` will install dependencies if not installed
--   `rake start` will run the server in production mode
--   `rake dev` will run the server in development mode
--   `rake dev_silent` will run the server in development mode with no logs
--   `rake build` will build a `.gem` file based on `tsurezure.gemspec`
-
-### actually using tsurezure:
-
-as for how to use tsurezure, here's a simple script to get started:
-
-```ruby
-require 'tsurezure'
-
-# create an instance of tsurezure
-server = Tsurezure.new(8888)
-
-# url: http://localhost:8888/user/1
-
-# create an endpoint
-server.register 'get', '/user/:id', lambda { |req|
-  url_vars = req[:vars] # { "id" => "1" }
-  params = req[:params] # {}
-
-  # create a respsonse for the endpoint
-  {
-    status: 200,
-    message: {
-      message: "hello user ##{url_vars['id']}!"
-    }.to_json
-  }
-}, content_type: 'application/json' # options hash
-
-# throw in some middleware
-server.add_middleware '/user/:id', lambda { |req|
-  url_vars = req[:vars]
-
-  # show a different response based on the request itself.
-  # if you return from middleware, the return value will
-  # be sent as the final response.
-  if req[:vars]['id'] == '1'
-    return {
-      status: 200, message: {
-      message: "hey user #1! you're the first one here!"
-    }.to_json
-  }
-
-  end
-}, content_type: 'application/json'
-
-#listen for connections
-server.listen
-```
-
-after you run this file, open up your browser or whatever and go to `http://localhost:8888/user/1`. you should see a json response that looks like this:
-
-```json
-{
-    "message": "hey user #1! you're the first one here!"
-}
-```
-
-the `listen` method can be called with no arguments to just start the server. you can also pass in a lambda or proc that will run when the server has started. the only argument that will be passed to that proc is a hash called `server_opts`. it contains some information about the current configuration:
-
-```ruby
-{
-  port, # port that tsurezure is running on
-  endpoints, # endpoints object containing the endpoints you've added
-  middleware # middleware object containing the middleware you've added
-}
-```
-
-simple example of usage:
-
-```ruby
-server.listen lambda { |opts|
-  puts "listening on port #{opts[:port]}!"
-}
-```
-
-the registration function for creating endpoints is very simple:
-
-```ruby
-register http_method, path, callback, options
-```
-
-`http_method` is the method to access the endpoint with. `path` is just the url.
-
-`path` can be a path that contains variables (such as `/user/:id`). see the example above to see how it works.
-
-`callback` is a lambda that contains the logic used to send a response. it will recieve one argument: the request that was sent to that endpoint. whatever is returned from the proc will be sent as the response from that endpoint.
-
-`options` is a hash containing various options to somehow modify the response. valid options:
-
--   `content_type (default: text/plain)` - determines the mime type of the response
--   `location` - if a location header is required (301, etc), this is used to provide it.
--   `method` - if an allow header is required (405), this is used to provide it.
-
-for middleware, it's much the same:
-
-```ruby
-add_middleware path, callback, options
-```
-
-`path` can be a path that contains variables. used in the same way as the `path` for endpoints.
-
-`callback` is a lambda that you can use to intercept and pre-process responses. if you return from a callback in middleware, then that return value will be sent as the final response.
-
-`options` for middleware are the same as the `options` for endpoints.
-
-* * *
-
-## todo
-
--   [ ]  make it so registered uris can only be accessed with the specified method, and everything else returns a 405 (maybe make this an option??)
-
--   [ ]  give the user an option to add middleware specifically for catching errors
-
-## misc
-
-disclaimer: I don't know ruby, and this is my first time using it to make something.
-
-the name comes from yukueshirezutsurezure, one of my favorite bands. it's pronounced 'tsɯ-ɾe-dzɯ-ɾe.'
+# tsurezure
+
+this is a simple web server framework written in ruby. mainly made as a way for me to quickly put together rest apis in my favorite language.
+
+it can be used in a very similar manner to the javascript framework express.
+
+* * *
+
+## usage
+
+### installing (from rubygems)
+
+just run `gem install tsurezure` and you'll have whatever the latest version is that I've put up.
+
+### installing (from source):
+
+requires:
+
+-   ruby
+-   nodejs + nodemon (**only** for hot reloading server in development mode, not necessarily required)
+
+after cloning this repo, from the root project directory, just run `rake start` to start in production mode, or `rake dev` to run in development mode, which adds hot reloading with nodemon. gem dependencies will install automatically.
+
+to build the gem: run `gem build tsurezure.gemspec`. then, install using `gem install tsurezure-version-number`. `version-number` is whatever version is installed based on the `.gemspec` file.
+
+### commands
+
+-   `rake install` will install dependencies
+-   `rake check_deps` will install dependencies if not installed
+-   `rake start` will run the server in production mode
+-   `rake dev` will run the server in development mode
+-   `rake dev_silent` will run the server in development mode with no logs
+-   `rake build` will build a `.gem` file based on `tsurezure.gemspec`
+
+### actually using tsurezure:
+
+as for how to use tsurezure, here's a simple script to get started:
+
+```ruby
+require 'tsurezure'
+
+# create an instance of tsurezure
+server = Tsurezure.new 8888
+
+# url: http://localhost:8888
+
+# create an endpoint
+server.register 'get', '/user/:id', lambda { |req|
+  url_vars = req[:vars] # { "id" => "1" }
+  params = req[:params] # {}
+
+  # create a respsonse for the endpoint
+  {
+    status: 200,
+    message: {
+      message: "hello user ##{url_vars['id']}!"
+    }.to_json
+  }
+}, content_type: 'application/json' # options hash
+
+# throw in some middleware
+server.add_middleware '/user/:id', lambda { |req|
+  url_vars = req[:vars]
+
+  # show a different response based on the request itself.
+  # if you return from middleware, the return value will
+  # be sent as the final response.
+  if req[:vars]['id'] == '1'
+    return {
+      status: 200, message: {
+      message: "hey user #1! you're the first one here!"
+    }.to_json
+  }
+
+  end
+}, content_type: 'application/json'
+
+#listen for connections
+server.listen
+```
+
+after you run this file, open up your browser or whatever and go to `http://localhost:8888/user/1`. you should see a json response that looks like this:
+
+```json
+{
+    "message": "hey user #1! you're the first one here!"
+}
+```
+
+the `listen` method can be called with no arguments to just start the server. you can also pass in a lambda or proc that will run when the server has started. the only argument that will be passed to that proc is a hash called `server_opts`. it contains some information about the current configuration:
+
+```ruby
+{
+  port, # port that tsurezure is running on
+  endpoints, # endpoints object containing the endpoints you've added
+  middleware # middleware object containing the middleware you've added
+}
+```
+
+simple example of usage:
+
+```ruby
+server.listen lambda { |opts|
+  puts "listening on port #{opts[:port]}!"
+}
+```
+
+the registration function for creating endpoints is very simple:
+
+```ruby
+register http_method, path, callback, options
+```
+
+`http_method` is the method to access the endpoint with. `path` is just the url.
+
+`path` can be a path that contains variables (such as `/user/:id`). see the example above to see how it works.
+
+`callback` is a lambda that contains the logic used to send a response. it will recieve one argument: the request that was sent to that endpoint. whatever is returned from the proc will be sent as the response from that endpoint.
+
+`options` is a hash containing various options to somehow modify the response. valid options:
+
+-   `content_type (default: text/plain)` - determines the mime type of the response
+-   `location` - if a location header is required (301, etc), this is used to provide it.
+-   `method` - if an allow header is required (405), this is used to provide it.
+
+for middleware, it's much the same:
+
+```ruby
+add_middleware path, callback, options
+```
+
+`path` can be a path that contains variables. used in the same way as the `path` for endpoints.
+
+`callback` is a lambda that you can use to intercept and pre-process responses. if you return from a callback in middleware, then that return value will be sent as the final response.
+
+`options` for middleware are the same as the `options` for endpoints.
+
+**anything** returned from a middleware will be interpreted as you trying to send a modified response. and of course, ruby will interpret the last reached statement in a method as an implicit return. to avoid this, if you want to have a middleware that doesn't necessarily send a response, just use a `return` at the end of your method to return `nil`.
+
+* * *
+
+## todo
+
+-   [ ]  make it so registered uris can only be accessed with the specified method, and everything else returns a 405 (maybe make this an option??)
+
+-   [ ]  give the user an option to add middleware specifically for catching errors
+
+## misc
+
+disclaimer: I don't know ruby, and this is my first time using it to make something.
+
+the name comes from yukueshirezutsurezure, one of my favorite bands. it's pronounced 'tsɯ-ɾe-dzɯ-ɾe.'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: tsurezure
 version: !ruby/object:Gem::Version
-  version: 0.0.31
+  version: 0.0.32
 platform: ruby
 authors:
 - jpegzilla
@@ -14,22 +14,16 @@ dependencies:
   name: json
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.8'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.3
+        version: 2.3.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.8'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.3
+        version: 2.3.0
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement