In some casese you don't want (or can't) to run all your project backend locally. Instead of it you prefer to use production server or any other environment as backend. It happens when you want to debug any complex issue which happens only for specific cu
An i18next backend plugin to work with both local resources and remote backend.
A connect based middleware to support local development against a remote backend.
A connect based middleware to support local development against a remote backend.
Proxy remote backend for local development with CORS and Cookies
Firebase JavaScript library for web and Node.js
Remote backend contract for Hookplane
Theia - Remote
SSH remote port forward
HTML5 backend for React DnD
Get the remote origin URL of a Git repository
The Remote Config package of the Firebase JS SDK
The compatibility package of Remote Config
Yjs encoding protocols
i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.
Jaeger binding for OpenTracing API for Node.js
Folder browser plugin for inquirer-gui
Appium proxy for Remote Debugger protocol
A wrapper of the `@mdx-js/mdx` for the `nextjs` applications in order to load MDX content. It is a fork of `next-mdx-remote`.
Rush plugin for generic HTTP cloud build cache
No description provided.
Core API used by Backstage backend plugins
Clerk Backend SDK - REST Client for Backend API & JWT verification utilities
Adds support for fetching translation from a remote resource
A gem to index/query ruby objects to/from remote backends
Hiera Server separates the query and the data retrieval into separate processes. The *server* portion runs on a remote machine and uses any configured Hiera backend to retrieve data. The *client* portion simply runs as a backend on the local machine. Facilities are provided to configure the data lookup on the server from either end. See README.md for more information.
Ruby client for integrating a ruby application with a remote ActionCable-based backend provided by Rails 5 or compatible framework. It allows for subscription and publication to multiple _channels_ simultaneously, and eavesdropping on wire-level messages. Harness the power of WebSockets to receive push notifications in your own Ruby applications!
A library for uploading files to multiple remote storage backends like Amazon S3 and Rackspace CloudFiles.
In combination with the i18n gem Simple backend, using the i18n_remote allows fetching data remotely
Nexoform wraps Terraform to provide awareness for multiple environments. Nexoform also provides a more guided experience for using remote backends to track your state. Without nexoform, there are several ways to accidentally lose or corrupt your current state. Nexoform puts up guard rails to prevent accidents, and puts you on firm ground with terraform.
Run Stable Diffusion from Ruby. Supports local Python subprocess (SDXL) and remote Modal GPU endpoints (SD 3.5). Handles S3 file transfer, presigned URLs, and automatic backend dispatch.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace
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.