Open Source Linux Cloud Services Software - Page 8

The Open Fabrics Interfaces (OFI) is a framework focused on exporting fabric communication services to applications. Libfabric pre-built binaries may be available from other sources, such as Linux distributions. Elastic Fabric Adapter (EFA) is a network interface for Amazon EC2 instances that enables customers to run applications requiring high levels of inter-node communications at scale on AWS. Its custom-built operating system (OS) bypass hardware interface enhances the performance of inter-instance communications, which is critical to scaling these applications. With EFA, High Performance Computing (HPC) applications using the Message Passing Interface (MPI) and Machine Learning (ML) applications using NVIDIA Collective Communications Library (NCCL) can scale to thousands of CPUs or GPUs. As a result, you get the application performance of on-premises HPC clusters with the on-demand elasticity and flexibility of the AWS cloud.

this project aims to create the most simple basics to create simple json-services to support mobile platforms and the most easy integration with the existing services.

Simple Firebase authentication for all Next.js rendering strategies. This package makes it simple to get the authenticated Firebase user and ID token during both client-side and server-side rendering (SSR). We treat the Firebase JS SDK as the source of truth for auth status. When the user signs in, we call an endpoint to generate a refresh token and store the user info, ID token, and refresh token in cookies. Future requests to SSR pages receive the user info and ID token from cookies, refreshing the ID token as needed. When the user logs out, we unset the cookies. This package will likely be helpful if you're using Firebase authentication and expect to use server-side rendering—especially if you need access to Firebase ID tokens on the server side. If your app only uses static pages or doesn't need the Firebase user for SSR, use the Firebase JS SDK directly to load the user on the client side.

A basic GNU Octave implementation of mqtt toolkit using the paho-mqtt library

The AWS OpsWorks Cookbooks repository provides the built-in Chef cookbooks used by the now-deprecated AWS OpsWorks Stacks service, a configuration-management and application-deployment service that used Chef (and optionally Puppet) to manage fleets of EC2 instances. These cookbooks implemented standard tasks such as package installation, web server configuration, database setup, Ruby/PHP/Java application deployment, and integration with AWS stack lifecycle events (setup, configure, deploy, shutdown). Customers could use these cookbooks as-is or extend/override them by supplying custom Chef recipes. Although OpsWorks Stacks reached end-of-life in May 2024, the repository remains valuable for teams still running legacy stacks or studying Chef automation patterns in an AWS context. The repository includes multiple branches to support different Chef versions (11.10, 11.4, 0.9) and provides reference implementation of layer recipes, attributes, and templates.

Supports display of all item types: stories, jobs, polls and comments. Basic user profiles. Collapsible comment threads, with child counts. "Realtime" updates (free via Firebase!). Last visit details for stories are cached in localStorage. New comments are highlighted. Comments since your last visit to an item. New comments which load while you're reading an item. New comments in collapsed threads. Automatic or manual collapsing of comment threads that don't contain any new comments. Manual highlighting of the X most recent comments to catch up on threads you were reading elsewhere. Stories with new comments are marked on list pages. Stories can be marked as read to remove highighting from new comments. "Comments" sections are driven by the Changed Items API. Story listing pages are cached in sessionStorage for quick back button usage and pagination in the same session. Configurable settings. Auto collapse - automatically collapses comment threads without new comments on page load.

React native module for firebase cloud messaging and local notification. react-native-firebase now can do what react-native-fcm can so it is a waste of effort to build the same thing in parallel. To allow android to respond to click_action, you need to define Activities and filter on specific intent. Since all javascript is running in MainActivity, you can have MainActivity to handle actions. If you are using RN < 0.30.0 and react-native-fcm < 1.0.16, pass intent into package, edit MainActivity.java. Import libraries, add Capabilities (background running and push notification), upload APNS and etc. Put frameworks under ios/Frameworks folder, and drag those files into your xcode solution. Make sure the file is not just moved into the folder. You need to Right Click the project folder in XCode and Add File to <Project Name>. Select Copy if needed in the Options page while selecting the file.

Redux bindings for Firebase. Includes Higher Order Component (HOC) for use with React. If you are starting a new project and/or are not required to have your Firebase data loaded into redux, you might want to give reactfire a try before trying react-redux-firebase. I wrote up a quick medium article explaining a bit about how, and why and showing how to start a new project with these tools. Out-of-the-box support for authentication (with auto-loading user profile from database/firestore). Full Firebase Platform Support Including Real-Time Database, Firestore, and Storage. Automatic binding/unbinding of listeners through React Hooks (useFirebaseConnect, useFirestoreConnect) or Higher Order Components (firebaseConnect and firestoreConnect). Population capability (similar to mongoose's populate or SQL's JOIN). Support small data ( using value ) or large datasets ( using child_added, child_removed, child_changed).

Serverless Chrome contains everything you need to get started running headless Chrome on AWS Lambda (possibly Azure and GCP Functions soon). The aim of this project is to provide the scaffolding for using Headless Chrome during a serverless function invocation. Serverless Chrome takes care of building and bundling the Chrome binaries and making sure Chrome is running when your serverless function executes. In addition, this project also provides a few example services for common patterns (e.g. taking a screenshot of a page, printing to PDF, some scraping, etc.). Why? Because it's neat. It also opens up interesting possibilities for using the Chrome DevTools Protocol (and tools like Chromeless or Puppeteer) in serverless architectures and doing testing/CI, web-scraping, pre-rendering, etc. You must configure your AWS credentials either by defining AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environmental variables, or using an AWS profile.

The only complete, end-to-end microservices management platform, SOAJS eliminates the IT plumbing challenges, so you can deploy microservices significantly earlier and faster. IT initiatives such as digital transformation are simplified, accelerated, cost reduced, and risk mitigated. Our fully integrated, world-class API lifecycle management, multi-cloud orchestration, release management, and IT Ops automation capabilities eliminate your IT organization’s modernization pain.

Accessing server-side mongodb through client javascript API. This project is a branch of dbcloud You can do almost invoke on mongodb through the javascript API in browser. The client javascript api support IE6.0+ Chrome FireFox and Wechat