![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
bundler_local_development
Advanced tools
Since this gem overrides bundler itself, it is installed and required in an unusual way. It is required within your Gemfile, and is not meant to be used in your application.
Add these lines to your application's Gemfile:
gem 'bundler_local_development', :group => :development, :require => false
begin
require 'bundler_local_development'
Bundler.development_gems = [/foo/, 'bar', /baz/]
rescue LoadError
end
And then execute:
$ bundle
Bundler.development_gems = [...]
in your Gemfile, to configure
your default set of local gems.
You can provide regular expressions or strings to match gem names.$DEV_GEMS
environment variable to add extra gems to this list (semicolon separated list of gem names).If the $GEM_DEV
environment variable is unset, this gem will have no effect.
If the $GEM_DEV
environment variable is set:
Bundler will search for local gems in the
path specified by $GEM_DEV_DIR
. (The default search path is $HOME/code/gems
, if $GEM_DEV_DIR
is unset.)
You can specify multiple directories by separating paths with a semicolon, e.g.
$HOME/code/gems;$HOME/code/more_gems
If a local copy of the gem is found, it will add the :path => <path>
option to the gem
command.
It will scan the local gem's gemspec
and process any runtime dependencies.
It will also load and evaluate the local gem's Gemfile
.
The Gemfile will have any source
or gemspec
lines stripped, as well as removing the rake
gem.
(I found that rake
was often pegged at different versions.)
Gemfile.lock
will NOT be updated if this gem is activated.In order to make the most of this gem, you need a quick way to enable or disable it.
Add the following function to your ~/.bashrc
or ~/.zshrc
:
# Gem development shortcuts
# Toggle between gem development and production mode
# (Set / unset $GEM_DEV variable)
gdv() {
local flag_var="GEM_DEV"
if env | grep -q "^$flag_var="; then
unset $flag_var
else
export $flag_var=true
fi
}
Now you will be able to enable or disable the gem by typing: gdv
Finally, you might want to know whether or not the gem is enabled.
Add the following function to your ~/.bashrc
or ~/.zshrc
:
# When developing gems ($GEM_DEV is exported), display a hammer and pick
parse_gem_development() {
if env | grep -q "^GEM_DEV="; then echo "\[\e[0;33m\]⚒ "; fi
}
Then, use $(parse_gem_development)
to display the indicator in your prompt.
git checkout -b my-new-feature
)git commit -am 'Added some feature'
)git push origin my-new-feature
)FAQs
Unknown package
We found that bundler_local_development demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.