Makes sure that all required environment variables are set.
Check that the critical environment variables are set
Check that the critical environment variables are set
Environment variables checker (CLI)
check env and return checked env valued
Check environment variables expected by CDK are set in your codebase
Validate AI agent configurations: check env vars, API keys, endpoints, and connectivity in one command.
Check utility for the-framework
Tool to retrieve and check env vars
Vite.js plugin that makes build fail if a required environment variable(s) is missing
env value to JS value, check env val is boolean or others
Detect Node.JS (as opposite to browser environment). ESM modification
A Vite plugin to check that required environment variables are available at build time. Scans your code for calls to a specified function and ensures the environment variables referenced in those calls are defined.
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
Check env file against mandatory variables present in package.json file.
Detect Node.JS (as opposite to browser environment) (reliable)
Personal env variables validator
A Babel preset for each environment.
Offers getProxyForUrl to get the proxy URL for a URL, respecting the *_PROXY (e.g. HTTP_PROXY) and NO_PROXY environment variables.
Runtime agnostic JS utils
Verify that all environment variables used are available in the environment.
Validate your env variables using Ajv with .env file support using Node.js built-in parseEnv
AWS credential provider that sources credentials from known environment variables
Terminal and Web console for Kubernetes
A simple git commit message generator by OpenAI compaction model.
A simple CLI tool to run react native projects
Blazing fast Git hooks manager written in Rust. Drop-in replacement for Husky with 27x faster startup.
Check if your env can build fltk-rs
EnvCheck is a lightweight Ruby gem that ensures your required and optional environment variables are present and valid before your app boots. Features smart config discovery (.env_check.yml or config/env_check.yml), comprehensive type validation with 9 built-in validators, .env loading with dotenv, and professional CLI tools. Framework-agnostic design works with Rails 7.1+ through Rails 8.0+, Ruby 3.0+.
Allows you to syntax check roles, env, cookbooks - all in one.
Checks required env variables and its format using dotenv and .env.sample files. Sample files include validation documentation which is interpreted and used to validate your environment.
Capistrano3 check .env variables
Simplify checking pre-requisites (env. vars. & executables) for ruby scripts
Gem checks if all of required ENVs are setup
env-enforcer allows you to list your required ENV variables, and checks for their presence at deploy time.
Check if YAML files contain secrets that should be in ENV
Reads the keys of the env variable. Use envreader -h for help and check all commands.
StandardHealth is a mountable Rails engine providing /alive, /ready, and /diagnostics/env endpoints, with a configuration block for registering custom checks and a DSL for declaring required and recommended environment variables.
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", "~> 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.
Germinate is a tool for writing about code. With Germinate, the source code IS the article. For example, given the following source code: # #!/usr/bin/env ruby # :BRACKET_CODE: <pre>, </pre> # :PROCESS: ruby, "ruby %f" # :SAMPLE: hello def hello(who) puts "Hello, #{who}" end hello("World") # :TEXT: # Check out my amazing program! Here's the hello method: # :INSERT: @hello:/def/../end/ # And here's the output: # :INSERT: @hello|ruby When we run the <tt>germ format</tt> command the following output is generated: Check out my amazing program! Here's the hello method: <pre> def hello(who) puts "Hello, #{who}" end </pre> And here's the output: <pre> Hello, World </pre> To get a better idea of how this works, please take a look at link:examples/basic.rb, or run: germ generate > basic.rb To generate an example article to play with. Germinate is particularly useful for writing articles, such as blog posts, which contain code excerpts. Instead of forcing you to keep a source code file and an article document in sync throughout the editing process, the Germinate motto is "The source code IS the article". Specially marked comment sections in your code file become the article text. Wherever you need to reference the source code in the article, use insertion directives to tell Germinate what parts of the code to excerpt. An advanced selector syntax enables you to be very specific about which lines of code you want to insert. If you also want to show the output of your code, Germinate has you covered. Special "process" directives enable you to define arbitrary commands which can be run on your code. The output of the command then becomes the excerpt text. You can define an arbitrary number of processes and have different excerpts showing the same code as processed by different commands. You can even string processes together into pipelines. Development of Germinate is graciously sponsored by Devver, purveyor of fine cloud-based services to busy Ruby developers. If you like this tool please check them out at http://devver.net.
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.