Recursively require all files within a folder.
Utility to require multiple files in a folder tree with flexible options
eXtended Require: Folder requires and index.js toolkit.
Import / require folder(s) of any type of files, and evaluate / curry the results.
Synchronous validation of a path existing either as a file or as a directory.
Get the package name from a folder path
Infer the owner of a path based on the owner of its nearest existing parent
Computes specs to re-run when files change
Configuration management for the npm cli
ASP.NET Core SignalR Client
Easily exclude node_modules in Webpack bundle
Module to generate Windows installers for Electron apps
Cypress custom command and hooks to remove downloads folder
require_tree for node
Run a lifecycle script for a package (descendant of npm-lifecycle)
Upload statics to S3 server
Git/Subversion/Mercurial repository metadata parser
Create a hash checksum over a folder and its content - its children and their content
Retrieves a name:pathname Map for a given workspaces config
Node CLI or module to calculate folder size
A recursive stream of the files and directories in a given folder
A professional solution for consolidating all your JavaScript projects in one Git repo
Vite plugin for inlining all JavaScript and CSS resources
Static file serving and directory listing
Lets you easily define how to include hierarchies of ruby files, and also apply inclusion/exclusion filters for what to include
Lets you easily define how to include hierarchies of ruby files, and also apply inclusion/exclusion filters for what to include
Load or Require all files in the folder.
Easily and non-intrusively require files from sub-folders. Without polluting global namespace, or having modules clobber each other, include RequireDir and initialize it to get access to #dir and #dir_r
DSL to facilitate require/load of ruby files and folders
Simple Google Drive file uploader with autocreating required folders
Create dump file in temporary folder of root directory, if folder not present in dir then it will create one. Usage: open interactive prompt by typing 'irb' and require 'generate_dump_file'. again, require File.expand_path('../config/environment', __FILE__) and then run GenerateDumpFile.create
autoload_path it’s a very simple gem that allows you to search through a folder and it’s subfolders in search of files and automatically require them.
Ceedling provides a set of tools to deploy its guts in a folder or which can be required in a Rakefile. This makes that process more automatic.
Several tools for fast developing an ImpactJS Game, include generators and built-in server to run the game and weltmeister level editor right in the current project folder without require apache server and PHP configuration.
An autoloader that lets you use any module namespace with any folder structure and mix in manual requires.
## Overview Privileged Access Manager (PAM) is a Google Cloud native, managed solution to secure, manage and audit privileged access while ensuring operational velocity and developer productivity. PAM enables just-in-time, time-bound, approval-based access elevations, and auditing of privileged access elevations and activity. PAM lets you define the rules of who can request access, what they can request access to, and if they should be granted access with or without approvals based on the sensitivity of the access and emergency of the situation. ## Concepts ### Entitlement An entitlement is an eligibility or license that allows specified users (requesters) to request and obtain access to specified resources subject to a set of conditions such as duration, etc. entitlements can be granted to both human and non-human principals. ### Grant A grant is an instance of active usage against the entitlement. A user can place a request for a grant against an entitlement. The request may be forwarded to an approver for their decision. Once approved, the grant is activated, ultimately giving the user access (roles/permissions) on a resource per the criteria specified in entitlement. ### How does PAM work PAM creates and uses a service agent (Google-managed service account) to perform the required IAM policy changes for granting access at a specific resource/access scope. The service agent requires getIAMPolicy and setIAMPolicy permissions at the appropriate (or higher) access scope - Organization/Folder/Project to make policy changes on the resources listed in PAM entitlements. When enabling PAM for a resource scope, the user/ principal performing that action should have the appropriate permissions at that resource scope (resourcemanager.{projects|folders|organizations}.setIamPolicy, resourcemanager.{projects|folders|organizations}.getIamPolicy, and resourcemanager.{projects|folders|organizations}.get) to list and grant the service agent/account the required access to perform IAM policy changes. Note that google-cloud-privileged_access_manager-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-privileged_access_manager instead. See the readme for more details.
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.