Search Results for "id"

Express & Koa middlewares and Fastify & Hapi plugins for CLS-based request ID generation, batteries included. An out-of-the-box solution for adding request IDs into your logs. Check out this blog post that describes the rationale behind cls-rtracer. Automatically generates a UUID V1 value as the id for each request and stores it in AsyncLocalStorage. Optionally, if the request contains an X-Request-Id header, uses its value instead.

...If you pass route() a JavaScript object as a route parameter, Ziggy will use the registered route-model binding keys for that route to find the correct parameter value inside the object. If no route-model binding keys are explicitly registered for a parameter, Ziggy will use the object's id key.

...We follow the Node.js Long Term Support plan and only test against versions that are officially supported and have not reached their end-of-life date. You can use any arbitrary string as your application id and master key. These will be used by your clients to authenticate with the Parse Server. Parse provides SDKs for all the major platforms.

Redis storage for Koa session middleware/cache with Sentinel and Cluster support. koa-redis works with koa-generic-session (a generic session middleware for koa).

...You need to register a new application on both Facebook and Twitter to get your tokens by which users can grant access to your application, and log in using their social accounts. The session needs a random string to make sure the session id in the browser is random. That random string is used to encrypt the session id in the browser, Why? To prevent session id guessing. Each user has a username, password, social Id, and picture. If the user is logged in via username and password, then the social Id has to be null, and the if logged in via a social account, then the password will be null.