Results for request-pre

Request Pretreatment for Actix

{Marlowe}[https://github.com/KineticCafe/marlowe] is a Rack middleware that extracts or creates a request ID using a pre-defined header, permitting request correlation across multiple services. When using Rails, Marlowe automatically adds itself to the middleware before <tt>Rails::Rack::Logger</tt>. As of Marlowe 3.0, a Faraday middleware is provided (<tt>require 'marlowe/faraday'</tt>).

Pushes current local branch to remote with upstream at origin/[local-branch-name]. It also opens a new pull request browser window at a URL with customized query params, based on specified options, which pre-populates certain fields in the pull request. This is especially useful when supporting multiple PR templates within a code base.

A gem for implementing the transactional outbox pattern with support for HTTP requests and custom message pre-processing.

Authi is a Ruby gem designed to be used both in your client and server HTTP-based applications. It implements the authentication methods based on HMAC-SHA1 encryption algorithm and a pre-shared key.The gem will sign your requests on the client side and authenticate that signature on the server side. It will even generate the secret keys necessary for your clients to sign their requests. Find the documentaion to see how it works!

For those who are using PHP to build their sites and want a very simple framework in which to organize their files, trivial is the solution. It's one PHP file that can include a few other pre-determined PHP and HTML files based on the request URI. This very simple division of content, actions (controllers), and views allows for multiple people to easily work on a smaller project without the overhead of a larger framework.

# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 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

Mounts /rails/erd in your Rails app. On every request the gem introspects ActiveRecord models and renders a Mermaid ERD viewer with Stimulus-driven filters, zoom/pan, copy & download. No pre-generated HTML file.

This is a basic HTTP Live Streaming (HLS) server written in Ruby using the Rack interface. It serves MP3 audio files by converting them on-the-fly into HLS format (M3U8 playlist and MP3 segment files) using `ffmpeg`. Converted files are cached for subsequent requests. This server is designed for simplicity and primarily targets Video on Demand (VOD) scenarios where you want to stream existing MP3 files via HLS without pre-converting them.

http://www.engineyard.com/blog/2010/extending-rails-3-with-railties/ http://www.igvita.com/2010/08/04/rails-3-internals-railtie-creating-plugins/ h1. Morning Glory Morning Glory is comprised of a rake task and helper methods that manages the deployment of static assets into an Amazon CloudFront CDN's S3 Bucket, improving the performance of static assets on your Rails web applications. _NOTE: You will require an Amazon Web Services (AWS) account in order to use this gem. Specially: S3 for storing the files you wish to distribute, and CloudFront for CDN distribution of those files._ This version of Morning Glory works with Rails 3.x and Ruby 1.9.x h2. What does it do? Morning Glory provides an easy way to deploy Ruby on Rails application assets to the Amazon CloudFront CDN. It solves a number of common issues with S3/CloudFront. For instance, CloudFront won't automatically expire old assets stored on edge nodes when you redeploy new assets (the Cloudfront expiry time is 24 hours minimum). To fix this Morning Glory will automatically namespace asset releases for you, then update all references to those renamed assets within your stylesheets ensuring there are no broken asset links. It also provides a helper method to rewrite all standard Rails asset helper generated URLs to your CloudFront CDN distributions, as well as handling switching between HTTP and HTTPS. Morning Glory was also built with SASS (Syntactically Awesome Stylesheets) in mind. If you use Sass for your stylesheets they will automatically be built before deployment to the CDN. See http://sass-lang.com/ for more information on Sass.s h2. What it doesn't do Morning Glory cannot configure your CloudFront distributions for you automatically. You will manually have to login to your AWS Management Console account, "https://console.aws.amazon.com/cloudfront/home":https://console.aws.amazon.com/cloudfront/home, and set up a distribution pointing to an S3 Bucket. h2. Installation <pre> gem 'morning_glory' </pre> h2. Usage Morning Glory provides it's functionality via rake tasks. You'll need to specify the target rails environment configuration you want to deploy for by using the @RAILS_ENV={env}@ parameter (for example, @RAILS_ENV=production@). <pre> rake morning_glory:cloudfront:deploy RAILS_ENV={YOUR_TARGET_ENVIRONMENT} </pre> h2. Configuration h3. The Morning Glory configuration file, @config/morning_glory.yml@ You can specify a configuration section for every rails environment (production, staging, testing, development). This section can have the following properties defined: <pre> --- production: enabled: true # Is MorningGlory enabled for this environment? bucket: cdn.production.foo.com # The bucket to deploy your assets into s3_logging_enabled: true # Log the deployment to S3 revision: "20100317134627" # The revision prefix. This timestamp automatically generateed on deployment delete_prev_rev: true # Delete the previous asset release (save on S3 storage space) </pre> h3. The Amazon S3 authentication keys configuration file, @config/s3.yml@ This file provides the access credentials for your Amazon AWS S3 account. You can configure keys for all your environments (production, staging, testing, development). <pre> --- production: access_key_id: YOUR_ACCESS_KEY secret_access_key: YOUR_SECRET_ACCESS_KEY </pre> Note: If you are deploying your system to Heroku, you can configure your Amazon AWS S3 information with the environment variables S3_KEY and S3_SECRET instead of using a configuration file. h3. Set up an asset_host For each environment that you'd like to utilise the CloudFront CDN for you'll need to define the asset_host within the @config/environments/{ENVIRONMENT}.rb@ configuration file. As of June 2010 AWS supports HTTPS requests on the CloudFront CDN, so you no longer have to worry about switching servers. (Yay!) h4. Example config/environments/production.rb @asset_host@ snippet: Here we're targeting a CNAME domain with HTTP support. <pre> ActionController::Base.asset_host = Proc.new { |source, request| if request.ssl? "#{request.protocol}#{request.host_with_port}" else "#{request.protocol}assets.example.com" end } </pre> h3. Why do we have to use a revision-number/namespace/timestamp? Once an asset has been deployed to the Amazon Cloudfront edge servers it cannot be modified - the version exists until it expires (minimum of 24 hours). To get around this we need to prefix the asset path with a revision of some sort - in MorningGlory's case we use a timestamp. That way you can deploy many times during a 24 hour period and always have your latest revision available on your web site. h2. Dependencies h3. AWS S3 Required for uploading the assets to the Amazon Web Services S3 buckets. See "http://amazon.rubyforge.org/":http://amazon.rubyforge.org/ for more documentation on installation. h2. About the name Perhaps not what you'd expect; a "Morning Glory":http://en.wikipedia.org/wiki/Morning_Glory_cloud is a rare cloud formation observed by glider pilots in Australia (see my side project, "YourFlightLog.com for flight-logging software for paraglider and hang-glider pilots":http://www.yourflightlog.com, from which the Morning Glory plugin was originally extracted). Copyright (c) 2010 "@AdamBurmister":http://twitter.com/adamburmister/, released under the MIT license

The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.

Stīpa is a lightweight, zero-dependency HTTP/1.1 framework built entirely on Ruby stdlib. Features: - Pure stdlib (socket, thread, erb, json, securerandom) - HTTP/1.1 with keep-alive, SO_REUSEPORT, and TCP_NODELAY - Thread pool with bounded queue and graceful shutdown - Pre-compiled middleware stack with zero per-request overhead - ERB templates with layouts, partials, and Vue 3 island helpers - CLI generator for MVC and API-only applications - Structured logging in logfmt format - Named route parameters via regex captures

== ABOUT A simple program and library to conjugate french verbs. Parses responses to requests to an online reference site. === Executable ConjugateFR comes with the executable binary +conjugatefr+. To view information about it's supported arguments, run conjugatefr --help === Custom Renderers To make a custom renderer, just type require conjugatefr/renderer and then make a class that extends +Renderer+. An example is as follows: require 'conjugatefr/renderer' class ExampleRenderer &lt; Renderer def pre puts "This goes before the words." end def word (name, words) print "#{name}:" words.each do |word| print " #{word}" end end def post puts "This goes after the words." end def description; "Renders an example format."; end end # Add to the Renderers list (For CLI and other programs that use it.) $renderers["Example"] = ExampleRenderer.new To try this out, save it as +erend.rb+ and then run: conjugatefr -R ./erend.rb -r Example It will produce the output: This goes before the words. someword: someconjugation etc etc ... (more words will be here) This goes after the words. === The Library The library can be included with +require conjugatefr+. It includes the +ConjugateFR+ class.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.