Generic service template
Schematics specific to Angular
OCI NodeJS client for Generic Artifacts Content Service
OC-Generic-Template-Compiler
OC-Generic-Template-Renderer
OpenTelemetry instrumentation for `generic-pool` resource pool for managing expensive resources
app-builder precompiled binaries
Basic access to the Mac OS X Keychain
This monorepo's version of "lodash". This package contains shared generic utilities that can be used within the ecosystem. This package should not have dependencies, and should not contain any references to the Analytics domain.
Generic resource pooling for Node.JS
The AsyncAPI generator. It can generate documentation, code, anything!
Nexus TypeScript SDK
Helper for building generic names, similar to webpack
Framework for decorating a TypeScript language service with support for languages embedded in template strings
Cooperative scheduler for the browser environment.
A simple service worker used for the static template in sandpack, allowing users to develop websites like they would locally in the browser.
Standalone TypeScript project service wrapper for linting.
Extensibility template for generating a generic App Builder action
A nestjs-cls plugin for transactional decorators
A data loading utility to reduce requests to a backend via batching and caching.
A JavaScript template literal tag that parses GraphQL queries
Fetch API compliant HTTP Server adapter
A generic toolkit to help with accessibility
No description provided.
Provides template generators for service abstractions
This gem is generate api template for Cloud Foundry Service Broker API.
MCG is a web daemon that automatically generate file from template and execute commands for web services deployed on Apache Mesos and Marathon.
This is the real deal! Download and Install away! Ruby on Skis provides a template for your wxRuby project. The template provides a directory structure, a set of Rakefiles to manage, and most importantly, to _package_ your Ruby application for distribution as a standalone program. It also includes an environment to get the application running and provide basic services to the program code. For now, the template only supports packaging for Mac OSX -and Windows-, although various flavors of Linux should be easily accommodated and are planned for the future. Note: Windows support has been removed in favor of getting a working generator and distributable gem in place.
Torquebox (http://www.torquebox.org) is a JBoss Application Server that will run your Rack and Rails apps in JRuby. Torquebox provides a number of additional functionality that you might find useful, such as messaging, background services, and scheduled tasks. Configuring those is incredibly easy, since they all rely on simple YAML file configs. This CLI application simplifies that further by lettnig you generate your applications and application templates with simple command line executions.
RESTRack is a Rack-based MVC framework that makes it extremely easy to develop RESTful data services. It is inspired by Rails, and follows a few of its conventions. But it has no routes file, routing relationships are done through supplying custom code blocks to class methods such as "has_relationship_to" or "has_mapped_relationships_to". RESTRack aims at being lightweight and easy to use. It will automatically render JSON and XML for the data structures you return in your actions (any structure parsable by the "json" and "xml-simple" gems, respectively). If you supply a view for a controller action, you do that using a builder file. Builder files are stored in the view directory grouped by controller name subdirectories (`view/<controller>/<action>.xml.builder`). XML format requests will then render the view template with the builder gem, rather than generating XML with XmlSimple.
A set of [mustache] templates extending [tla-trace-filter] -tool to create a self extracting achieve for API traces generated, when model checking formal models created by [tla-Sbuilder] -tool. Also includes Ruby classes to extract test cases from archive extract. Use case: Formal models, built using [tla-sbuilder], and model checked using [TLA+tools]], can generate /API Traces/, which represent end-to-end scenarios executing across system services in the formal model. An API Trace is composed of steps, with each step giving 1) a (formal) system state before the API call, 2) the API call exercised together with (formal model) value bindings of request parameters, 3) API response returned, and 4) the (formal) system state after the API call. A API Trace can be mapped to /Unit Tests/ on implementation with each Unit Test corresponding a step in the API Trace. After executing each of the individual Unit Tests, the aggregate result can be interpreted as an execution of a "virtual" System Test - considerably easier than managing the execution a System Test as a single unit. The purpose of =tla-trace-arch= GEM is create a self extracting archive, which can be safely distributed to system service developers for extracting API Trace Steps to create unit tests for the service being developed by the developer. Ref: - https://github.com/jarjuk/tla-trace-filter - https://mustache.github.io/mustache.5.html - https://github.com/jarjuk/tla-sbuilder - http://research.microsoft.com/en-us/um/people/lamport/tla/tools.html
# 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
No description provided.
No description provided.
No description provided.
No description provided.