Run a command using sudo, prompting the user with an OS dialog if necessary
Run a command using sudo, prompting the user with an OS dialog if necessary
Block users from running your app with root permissions
Try to downgrade the permissions of a process with root privileges and block access if it fails
Check if the process is running as root user, for example, one started with `sudo`
A JavaScript implementation of the elasticsearch Query DSL
Native TUN/TAP interface module for Node.js
HTTPS server running on localhost
Bindings to native Mac/Linux/Windows password APIs
unixodbc bindings for node
VS Code Extensions Manager
Wrap sudo with optional password cache
Get OS key mapping
Try to downgrade the permissions of a process with root privileges
The Lodash method `_.omit` exported as a module.
Node.js libgit2 asynchronous native bindings
Bindings to native Mac/Linux/Windows password APIs
Canvas graphics API backed by Cairo
The Sudo Platform makes it seamless for developers to integrate Sudo capabilities into their existing applications with minimal effort. For applications that support Open ID Connect, the User SDK enables applications to map their existing users to a Sudo
The Lodash method `_.merge` exported as a module.
Easy direct access to the most recent official timezone information for iCalendar files via JavaScript/TypeScript
Find and parse local Capistrano configuration for a project.
Check if the process is running with elevated privileges
[](https://greenkeeper.io/)
capistrano plugin, for sudo operation with password input.
Capistrano Strategy for deployment of a project from source using sudo
This gem is a viable alternative to Git deployments on production machines. Commands are run under a different user than the `deploy` user.
A backend to be used in conjunction with Capistrano 3 and SSHKit to allow deployment on setups where users login as one identity and then need to sudo to a different identity for each command.
== FEATURES/PROBLEMS: * Failure is incredibly ungraceful, though generally unlikely, given that the requirements for accessing the Trac site are roughly the same as those for accessing the repository. * Currently, the trac user/pass must be the same as the SCM user/pass. It remains to be seen how much of a problem this will be. == SYNOPSIS: Include the recipes: require 'capistrano_trac/recipes' For the trac tasks to work, the :trac_url variable must be set to the root of your trac site. For example: set :trac_url, "http://www.yourtrachost/trac/yourproject" The 2 trac ticketing tasks are designed to be run in conjunction with a deployment or rollback, although this isn't mandatory. To automatically document deployments and rollbacks in your capistrano deployment, add the lines: * after "deploy", "trac:record_deployment" * before "deploy:rollback", "trac:record_rollback" Order is important, otherwise the tasks will be looking at the wrong revisions. To manually record changes, simply run the record_deployment task to document the most recent deployment changes, or the record_rollback task to document a rollback that is about to be run. == REQUIREMENTS: * capistrano >= 2.0.0 * mechanize >= 0.6.10 == INSTALL: * sudo gem install capistrano_trac == LICENSE: (The MIT License) Copyright (c) 2007 FIX Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: