Libraries tagged by envs
drupal/wisski_starter
156 Downloads
Installs and configures the WissKI base environment with mandatory modules.
divante-ltd/pimcore-document-copier
4220 Downloads
Pimcore bundle for copying documents between environments
devuri/ob-cache
3354 Downloads
A simple versatile and easy-to-use PHP class designed for managing caching in WordPress environments.
devgeniem/wp-noindex-testing-staging-robots
13110 Downloads
Uses robots.txt to not index development/testing environments of this site with search-engines
decodelabs/zest
1827 Downloads
Vite front end dev environment integration
davestewart/sketchpad
12918 Downloads
An innovative front-end environment for interactive Laravel development
dashifen/wp-debugging
4765 Downloads
A PHP trait that can be used by other objects for on-screen debugging within a WordPress environment.
conversador/conversador-php-sdk
5637 Downloads
Pacote para fácil instalação e utilização da API do Conversador para envio de mensagens.
comes/simpleauthenticator
9609 Downloads
A PHP library for implementing Google Authenticator's two-factor authentication (2FA) with Laravel, ensuring enhanced security for user authentication.
codemonauts/craft-aws
3826 Downloads
Plugin providing components and function to run Craft CMS in a high-available AWS environments.
clonixdev/php-aeat-sii
890 Downloads
Paquete para el envío y consulta de facturas con AEAT SII de españa utilizando la versión V 1.1
cajogos/php-temp-cache
583 Downloads
Simple PHP caching system that uses a tmp folder in a Linux environment.
briqpay/php-sdk
10717 Downloads
This is the API documentation for Briqpay. You can find out more about us and our offering at our website [https://briqpay.com](https://briqpay.com) In order to get credentials to the playgrund API Please register at [https://app.briqpay.com](https://app.briqpay.com) # Introduction Briqpay Checkout is an inline checkout solution for your b2b ecommerce. Briqpay Checkout gives you the flexibility of controlling your payment methods and credit rules while optimizing the UX for your customers # SDKs Briqpay offers standard SDKs to PHP and .NET based on these swagger definitions. You can download them respively or use our swagger defintitions to codegen your own versions. #### For .NET `` Install-Package Briqpay `` #### For PHP `` composer require briqpay/php-sdk `` # Standard use-case As a first step of integration you will need to create a checkout session. \n\nIn this session you provide Briqpay with the basic information necessary. In the response from briqpay you will recieve a htmlsnippet that is to be inserted into your frontend. The snippet provided by briqpay will render an iframe where the user will complete the purchase. Once completed, briqpay will redirect the customer to a confirmation page that you have defined.  # JavaScript SDK The first step of integration is to add our JS to your site just before closing the ```` tag. This ensures that our JS library is avaliable to load the checkout. ```` Briqpay offers a few methods avaliable through our Javascript SDK. The library is added by our iframe and is avalable on ``window._briqpay`` If you offer the posibility to update the cart or order amonts on the checkout page, the JS library will help you. If your store charges the customer different costs and fees depening on their shipping location, you can listen to the ``addressupdate``event in order to re-calculate the total cost. ```javascript window._briqpay.subscribe('addressupdate', function (data) { console.log(data) }) ``` If your frontend needs to perform an action whe the signup has completed, listen to the ``signup_finalized`` event. ```javascript window._briqpay.subscribe('signup_finalized', function (status) { // redirect or handle status 'success' / 'failure' }) ``` If you allow customers to change the total cart value, you can utilise the JS library to suspend the iframe while you perform a backen update call towards our services. As described below:  The iframe will auto-resume after 7 seconds if you dont call ``_briqpay.resume()`` before # Test Data In order to verify your integration you will neeed to use test data towards our credit engine. ## Company identication numbers * 1111111111 - To recieve a high credit scoring company ( 100 in rating) * 2222222222 - To test the enviournment with a bad credit scoring company (10 in rating) ## Card details In our playground setup your account is by default setup with a Stripe integration. In order to test out the card form you can use the below card numbers: * 4000002500003155 - To mock 3ds authentication window * 4000000000000069 Charge is declined with an expired_card code. You can use any valid expiry and CVC code # Authentication Briqpay utilizes JWT in order to authenticate calls to our platform. Authentication tokens expire after 48 hours, and at that point you can generate a new token for the given resource using the ``/auth`` endpoint. - Basic Auth - only used on the auth endpoint in order to get the Bearer Token - JWT Bearer Token - All calls towards the API utlizes this method"
brightmachine/scrutiny
2184 Downloads
Scrutiny checks over your environment to make sure your app is running as it should be – use Oh Dear or Pingdom to check it
boxuk/wp-feature-flags
579 Downloads
A feature flag manager and register for releasing features across environments.