Results for env-paths

Returns the directory where the cache is located. This is different for each os.

Automatically generate a requirement.txt file for Python projects

Environment specific paths. A port of node's env-paths

ruby script to append, prepend, remove, remove by regexp and remove duplicate entries from PATH (shell) variable. Use it to simplify environment setup from shell scripts

ruby script to append, prepend, remove, remove by regexp and remove duplicate entries from PATH (shell) variable. Use it to simplify environment setup from shell scripts

Rack middleware that abstracts format (extension) away from the path (into env).

Rack middleware that abstracts format (extension) away from the path (into env)

Course-grained access control based on URL path (env['PATH_INFO'])

1️⃣ Provides nomono_gems and eval_nomono_gems to standardize local multi-repo dependency wiring in Gemfiles.

Some convenient YAML-tags... - to get environment values: env, env?, env/integer, env/integer?, env/bool, env/bool?. - to create a Pathname (!path) or URI (!uri) - format a string: !str/format See README for examples.

cliblog is a command-line blog client. It loops waiting for command-line input, and if 'edit' or 'create' command is input, then it will launch user's favorite EDITOR brought from ENV variable. Or you can input your editor's path manually if ENV['EDITOR'] is not set. As for me, I'm using 'vim' for my personal typo-powered blog.

Fork of bundled mkmf.rb, should work as drop in replacement. Modifications: * GDB and XCode path compatibility: relative path specified by mkmf (../../../../ext/<target>/...) confuses source-to-debug correspondence. The downside to this is that mkmfmf specifies absolute paths, which means that the project will have to be recompiled for debugging from an alternate location. This can be disabled by adding a use_relative_paths block. * CURRENTLY NOT WORKING: Sub-directory support for source code: all .c, .m, .cc, .cxx., .cpp files and if the filesystem is case sensitive, all .C files are automatically included, and any directories with .h files are added to INCFLAGS. * Automatically uses CC from ENV if set

Chef-Berksfile-Env ================== A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile. This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`. View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed. Installation ------------ /opt/chef/embedded/bin/gem install chef-berksfile-env Usage ----- In your chef repo create a Berksfile next to your Chef environment file like this, chef-repo/environments/[ENV_NAME]/Berksfile This is the default location that will used by the plugin. We have to put the Berksfile in its own directory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247). The berksfile should include any cookbooks that your nodes or roles explicitly mention for that environment, source "https://supermarket.getchef.com" cookbook "java" cookbook "yum", "~&gt; 2.0" ... Next we need to generate our Berksfile's lock file, berks install Your environment file must by in `.rb` format and look like this, require 'chef-berksfile-env' # The name must be defined first so we can use it to find the Berksfile name "my_env" # Load Berksfile locked dependencies as my environment's cookbook version contraints load_berksfile ... Now our environment will use the locked versions of the cookbooks and transitive dependencies generated by our Berksfile. Upgrading to the latest dependecies is now as simple as, berks install Our Berksfile also provides an easy way to ensure all the cookbooks and their versions that our environment requires are uploaded to our chef-server, berks upload How the Plugin Finds the Berksfile ---------------------------------- If you are curious how the plugin knows to find the Berksfile in `chef-repo/environments/[ENV]/Berksfile`, you want to put your Berksfile somewhere else or you have run into this error `Expected Berksfile at [/path/../Berksfile] but does not exist`, this section will explain how this works and ways to tweak the path or fix your error. `load_berksfile` has an optional argument which represents the path to your Berksfile. This path can be pseduo relative (explained in a moment) or absolute. By default the value is `environments/[ENV_NAME]/Berksfile`. By pseduo relative I mean that its a relative path but the plugin will check to see if the directory we are executing from partially matches our relative path. So if we are running knife from `/home/chef-repo/environments` and our relative path is `chef-repo/environments/dev/Berksfile` the plugin will see that the relative path is partially included in our execution directory and will attempt to merge the two to come up with `/home/chef-repo/environments/dev/Berksfile`. If we can't make any match at all we attempt to guess the path by just joining the relative path with our execution directory. So why do we do this? Well the only way to use this plugin is if your environment is in Ruby format. Chef's `knife from file ...` uses Ruby's `instance_eval` in order to do this. This means the code on Chef's end effectively looks like this, env.instance_eval(IO.read(env_ruby_file)) which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment Ruby file, so instead we guess.

StratoEnv populates ENV from one or more AWS SSM Parameter Store paths. Multiple paths form layers, with later paths overriding earlier ones, so you can split common config from node-specific or environment-specific overrides. No Rails dependency; works in Rails, Sinatra, Lambda, scripts, or any Ruby boot process.

No description provided.

No description provided.