Open Source JavaScript Cloud Services Software - Page 2

Upon successful authentication, a cookie (named TOKEN) with the value of a signed JWT is set and the user redirected back to the originally requested path. Upon each request, Lambda@Edge checks the JWT for validity (signature, expiration date, audience and matching hosted domain) and will redirect the user to configured provider's login when their session has timed out. If your CloudFront distribution is pointed at a S3 bucket, configure origin access identity so S3 objects can be stored with private permissions. (Origin access identity requires the S3 ACL owner be the account owner. Use our s3-object-owner-monitor Lambda function if writing objects across multiple accounts.) Enable SSL/HTTPS on your CloudFront distribution; AWS Certificate Manager can be used to provision a no-cost certificate. Session duration is defined as the number of hours that the JWT is valid for. After session expiration, cloudfront-auth will redirect the user to the configured provider to re-authenticate.

The most used, flexible, fast and streaming parser for multipart form data. Supports uploading to serverless environments, AWS S3, Azure, GCP or the filesystem. Used in production. This project is semantically versioned and available as part of the Tidelift Subscription for professional-grade assurances, enhanced support and security. The maintainers of formidable and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the Open Source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Of course, with Koa v1, v2 or future v3 the things are very similar. You can use formidable manually as or through the koa-better-body package which is using formidable under the hood and support more features and different request bodies, check its documentation for more info.

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.

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.

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.

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