nodejs zk hessian java
[Fork of joeferner/node-java] Bridge API to connect with existing Java APIs.
The node version FHIR validator that use node-java call java FHIR's APIs
enables platform independent java support
Utility for Node's java module to load mvn dependencies.
Utility for Node's java module to load mvn dependencies.
Node.js API and bindings supporting java.lang and java.util. * (partial) support for java.lang based on node-java * (partial) support for java.util based on node-java. * Basic abstraction on top of node-java * typings for node-java * Projects l
Utilities for using Tinkerpop3 via the node-java API in Typescript
Node.js wrapper for SourceAFIS for Java via node-java
Node Module JDBC wrapper updated to Node Java 0.10.0
A lightweight crypto library which could run on `browser`, `node`, `java(jvm)`, `dotnet` platform base on `openssl libcrypto library`.
Wrapper for the node-java npm package that improves locating the JRE on the target machine and can support multiple prebuilt platform builds
Find JAVA_HOME on any system
Library to easily call java from node sources. Automatically installs java if not present
Bridge API to connect with existing Java APIs.
Java language support for the CodeMirror code editor
lezer-based Java grammar
Datadog CI plugin for `aas` commands
Utility for Node's java module to load mvn dependencies.
Port of Log4js to work with node.
Java Parser in JavaScript
Java dictionary for cspell.
Reads and interpolates Java .properties files
A JavaScript API for generating wallet and signing transaction in wechat. The AES encrypt/decrypt is compatible with node/java sdk.
This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program
Idiomatic Ruby bindings for PDF Oxide. Process, analyze, and generate PDFs through the libpdf_oxide cdylib used by the Python, Java, Node, Go, and C# bindings.
Diff and patch tables
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.
Diff and patch tables
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.