Minimalist-friendly ~1.5KB router for React
MCP server for APIMesh — 76 x402-payable tools for AI agents (74 APIs + wallet usage + spend caps). Covers web vitals, security headers, SEO audits, email security and verification, tech-stack detection, brand assets, redirect chains, indexability, brand
Check if a number is a redirect HTTP status code
Utility functions for requester implementatons used in @gitbeaker
Core API implementation of the GitLab API
Cross Platform implementation of the GitLab API
Parses netlify redirects into a js object representation
MJML: the only framework that makes responsive-email easy
Parses netlify redirects into a js object representation
Produces redirects (HTTP redirections) for pages in an Antora site.
🍪 Simple cross-browser cookie-consent plugin written in vanilla js.
Process execution for humans
<p align="center"> <img src="https://github.com/vueuse/vue-demi/blob/main/assets/banner.png?raw=true" width="600"/> <br> <a href='https://www.npmjs.com/package/vue-demi'><img src='https://img.shields.io/npm/v/vue-demi?color=42b883' alt='npm'></a> </p>
Universal React avatar component makes it possible to generate avatars based on user information.
Minimalist-friendly ~1.5KB router for Preact
Elegant Console Wrapper
A plugin to add redirect URL functionality to Algolia Autocomplete.
SDK for 'Sign in with LiveChat'.
Argo CD MCP Server
Check if the given request is HTTPS
Asset support code for React Native.
A window.fetch polyfill.
Mailgun email sender for Constructive
Add redirect pages to your generated TypeDoc site.
Rack middleware which will redirect every 404 assets requests to the current digested version for the logical_path referenced in the manifest. Useful to automate redirects from deleted assets when the old link can't be updated, e.g. emails.
Rack middleware which will look up your assets manifest file and redirect a request with no digest in the file name to the version with digest in the file name.
Automatically makes your Rails app loading content in the background via ajax. Works by turning all internal links into ajax links that trigger an update of the page's content area. Also form submissions are automatically turned into ajax requests. Uses the html5 history interface for changing the url and making the browser's back and forward buttons working with ajax. Falls back to a hash based approach for browsers without the history interface (like Internet Explorer <10). Transparently handles redirects and supports flash messages and page titles. Requires Ruby 1.9 and the asset pipeline.
Sinatra-rraoute provides `gget'/`ppost'/`ddelete'/... methods which work just like Sinatra's built-in `get'/`post'/`delete'/... methods, but which map named routes to functions so that they can be referenced in redirects etc. The `path' helper will return a route for a certain route name and the given values for this route and comes in handy in both, the controller/model component of the application, and the view where you can use it to render links, assets URLs, AJAX calls... The nestable `nnamespace' method is useful for API versioning and does not interfere with other namespace extensions for Sinatra.
# Payfast Payfast is a Ruby gem that simplifies the process of integrating the PayFast payment gateway into your Ruby on Rails application. It provides a generator that helps scaffold the necessary configuration, routes, models, and controllers required to integrate PayFast seamlessly. ## Demo  ## Installation Add this line to your application's Gemfile: ```bash bundle add payfast ``` ## Usage ```bash rails generate payfast:install ``` ## This generator will perform the following actions: insert config/routes.rb create app/controllers/carts_controller.rb create app/views/carts/index.html.erb create app/views/carts/make_payment.html.erb create app/helpers/carts_helper.rb create db/migrate/20230824105530_create_carts.rb create config/payfast.yml create app/models/cart.rb insert app/views/layouts/application.html.erb insert config/environments/development.rb ## Additional configuration Setup payfast credentials for your environment rails EDITOR="code --wait" bin/rails credentials:edit This will allow you to securely edit and store your credentials. once you save and exit the file, the credentials will be encrypted and can only be accessed withe rails master key. payfast: merchant_id: {your_merchant_id} merchant_key: {your_merchant_key} passphrase: {{your_passphrase}} ## Update your `payfast.yml` config file - setup the credentials to be use by the rails app - uncomment `Rails.application.credentials.payfast.merchant_id ` and wrap it in erb tags as instructed in the comments. ## Templates Update the `make_payment.html.erb` as instructed in the file. it should look like so: ```js <script> // set the uuid to uuid = @cart.payment_uid. surround @carts.payment_uid with erb tags const uuid = `<%= @cart.payment_uuid %>` window.payfast_do_onsite_payment({uuid}, function (result) { if (result === true) { // redirect success_path(@cart) window.location.href = `<%= success_cart_path(@cart) %>` } else { // Redirect to failure_path(@cart) window.location.href = `<%= failure_cart_path(@cart) %>` } }); </script> ``` ## Testing - payfast api allows only SSL communication from your server. inorder to test locally. you will have to use a tunneling service that allows you to expose your local development server to the internet. your rails development config has was modified by the generator to allow ngrok hosts to hit your rails server ```ruby config.hosts << /[a-z0-9-]+\.ngrok-free\.app/ ``` ## Contributing Thank you for considering contributing to our project! We welcome contributions from the community to help improve this project and make it better for everyone. ### Issues If you encounter any issues or bugs while using our project, please [open a new issue](https://github.com/mactunechy/payfast/issues) on GitHub. Please make sure to include detailed information about the problem, steps to reproduce it, and the environment in which you encountered it. ### Pull Requests We encourage pull requests from the community! If you have an improvement or new feature you'd like to contribute, please follow these steps: 1. Fork the repository and create a new branch for your feature or bug fix. 2. Make your changes and write tests to cover any new functionality. 3. Ensure that the existing tests pass and write additional tests for any bug fixes. 4. Commit your changes and push the new branch to your forked repository. 5. Submit a pull request to our main repository, including a detailed description of the changes you made and any relevant information. We will review your pull request as soon as possible and provide feedback if needed. We value your contributions and will work with you to ensure your changes are integrated smoothly. d Your contributions are essential to the success of this project, and we are grateful for your help in making it better for everyone. If you have any questions or need further assistance, feel free to reach out to us. Happy coding!
Contentful API wrapper library exposing an ActiveRecord-like interface