tdiary 5.4.0 → 5.5.0.beta1

data/vendor/bundle/ruby/3.4.0/gems/rackup-2.3.1/license.md

@@ -0,0 +1,80 @@
+# MIT License
+
+Copyright, 2007-2009, by Leah Neukirchen.  
+Copyright, 2008, by Marc-André Cournoyer.  
+Copyright, 2009, by Aaron Pfeifer.  
+Copyright, 2009-2010, by Megan Batty.  
+Copyright, 2009-2010, by Michael Fellinger.  
+Copyright, 2009, by Genki Takiuchi.  
+Copyright, 2009, by Joshua Peek.  
+Copyright, 2009, by Yehuda Katz.  
+Copyright, 2009, by Carl Lerche.  
+Copyright, 2010, by Julik Tarkhanov.  
+Copyright, 2010-2016, by James Tucker.  
+Copyright, 2010, by Timur Batyrshin.  
+Copyright, 2010, by Loren Segal.  
+Copyright, 2010, by Andrew Bortz.  
+Copyright, 2010, by John Barnette.  
+Copyright, 2010, by John Sumsion.  
+Copyright, 2011-2018, by Aaron Patterson.  
+Copyright, 2011, by Konstantin Haase.  
+Copyright, 2011, by Blake Mizerany.  
+Copyright, 2011, by Tsutomu Kuroda.  
+Copyright, 2012, by Jean Boussier.  
+Copyright, 2012, by Trevor Wennblom.  
+Copyright, 2012, by Anurag Priyam.  
+Copyright, 2012, by Hrvoje Šimić.  
+Copyright, 2013, by Uchio Kondo.  
+Copyright, 2013, by Tim Moore.  
+Copyright, 2013, by Hal Brodigan.  
+Copyright, 2013, by Bas Vodde.  
+Copyright, 2013, by Joe Fiorini.  
+Copyright, 2014, by Wyatt Pan.  
+Copyright, 2014, by Lenny Marks.  
+Copyright, 2014, by Igor Bochkariov.  
+Copyright, 2014, by Max Cantor.  
+Copyright, 2014, by David Celis.  
+Copyright, 2014-2019, by Rafael França.  
+Copyright, 2014, by Jeremy Kemper.  
+Copyright, 2014, by Richard Schneeman.  
+Copyright, 2015, by Peter Wilmott.  
+Copyright, 2015, by Sean McGivern.  
+Copyright, 2015, by Tadashi Saito.  
+Copyright, 2015, by Martin Hrdlicka.  
+Copyright, 2015, by Zachary Scott.  
+Copyright, 2016, by Sophie Deziel.  
+Copyright, 2016, by Kazuya Hotta.  
+Copyright, 2017, by Ryunosuke Sato.  
+Copyright, 2017-2024, by Samuel Williams.  
+Copyright, 2018, by Dillon Welch.  
+Copyright, 2018, by Yoshiyuki Hirano.  
+Copyright, 2018, by Nick LaMuro.  
+Copyright, 2019, by Krzysztof Rybka.  
+Copyright, 2019, by Misaki Shioi.  
+Copyright, 2020-2022, by Jeremy Evans.  
+Copyright, 2021, by Katsuhiko Yoshida.  
+Copyright, 2021, by Kang Sheng.  
+Copyright, 2021, by Stephen Paul Weber.  
+Copyright, 2022, by Akira Matsuda.  
+Copyright, 2022, by Andrew Hoglund.  
+Copyright, 2024, by Olle Jonsson.  
+Copyright, 2024, by Geremia Taglialatela.  
+Copyright, 2024, by Petrik de Heus.  
+
+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.

data/vendor/bundle/ruby/3.4.0/gems/rackup-2.3.1/readme.md

@@ -0,0 +1,82 @@
+# Rackup
+
+`rackup` provides a command line interface for running a Rack-compatible application. It also provides a generic interface for starting a `rack`-compatible server: `Rackup::Handler`. It is not designed for production use.
+
+[![Development Status](https://github.com/rack/rackup/workflows/Test/badge.svg)](https://github.com/rack/rackup/actions?workflow=Test)
+
+## Installation
+
+``` bash
+-- For Puma
+$ gem install rackup puma
+
+-- For Falcon
+$ gem install rackup falcon
+```
+
+## Usage
+
+In a directory with your `config.ru` simply run the command:
+
+``` bash
+$ rackup
+```
+
+Your application should now be available locally, typically `http://localhost:9292`.
+
+### Server Handler
+
+You can also use `Rackup::Handler` to start a server programmatically:
+
+``` ruby
+require 'rackup'
+
+# Use the default server:
+handler = Rackup::Handler.default
+handler.run(app, **options)
+
+# Use a specific server:
+handler = Rackup::Handler.get('puma')
+handler.run(app, **options)
+```
+
+Do not require specific handlers or assume they will exist/work. Instead, use the `default` method to get the best available handler.
+
+## (Soft) Deprecation
+
+For a long time, `rackup` (the executable and implementation) was part of `rack`, and `webrick` was the default server, included with Ruby. It made it easy to run a Rack application without having to worry about the details of the server - great for documentation and demos.
+
+When `webrick` was removed from the Ruby standard library, `rack` started depending on `webrick` as a default server. Every web application and server would pull in `webrick` as a dependency, even if it was not used. To avoid this, the `rackup` component of `rack` was moved to this gem, which depended on `webrick`.
+
+However, many libraries (e.g. `rails`) still depend on `rackup` and end up pulling in `webrick` as a dependency. To avoid this, the decision was made to cut `webrick` as a dependency of `rackup`. This means that `rackup` no longer depends on `webrick`, and you need to install it separately if you want to use it.
+
+As a consequence of this, the value of the `rackup` gem is further diminished. In other words, why would you do this:
+
+``` bash
+$ gem install rackup puma
+$ rackup ...
+```
+
+when you can do this:
+
+``` bash
+$ gem install puma
+$ puma ...
+```
+
+In summary, the maintainers of `rack` recommend the following:
+
+  - Libraries should not depend on `rackup` if possible. `rackup` as an executable made sense when webrick shipped with Ruby, so there was always a fallback. But that hasn't been true since Ruby 3.0.
+  - Frameworks and applications should focus on providing `config.ru` files, so that users can use the webserver program of their choice directly (e.g. puma, falcon).
+  - There is still some value in the generic `rackup` and `Rackup::Handler` interfaces, but we encourage users to invoke the server command directly if possible.
+  - Webrick should be avoided if possible.
+
+## Contributing
+
+We welcome contributions to this project.
+
+1.  Fork it.
+2.  Create your feature branch (`git checkout -b my-new-feature`).
+3.  Commit your changes (`git commit -am 'Add some feature'`).
+4.  Push to the branch (`git push origin my-new-feature`).
+5.  Create new Pull Request.

data/vendor/bundle/ruby/3.4.0/gems/rackup-2.3.1/releases.md

@@ -0,0 +1,28 @@
+# Releases
+
+All notable changes to this project will be documented in this file. For info on how to format all future additions to this file please reference [Keep A Changelog](https://keepachangelog.com/en/1.0.0/).
+
+## v2.2.1
+
+  - Try to require `webrick` and `rackup/handler/webrick` by default, for compatibility with code that expects them to be available.
+
+## v2.2.0
+
+  - Remove old rack shims.
+  - Remove `webrick` dependency.
+
+## v2.1.0
+
+  - Correctly support streaming responses with `webrick`.
+
+## v2.0.0
+
+  - Initial release and migration of code from `rack`.
+
+## v1.0.1
+
+  - Fix `rackup.rb` invalid requires.
+
+## v1.0.0
+
+  - Initial release of empty shim for Rack v2.

data/vendor/bundle/ruby/3.4.0/gems/rackup-2.3.1/security.md

@@ -0,0 +1,3 @@
+# Security Policy
+
+Please see our main security policy: https://github.com/rack/rack/security/policy