Bulk is an application deployment system for container and cloud servers.
The goal of Bulk is to be the layer between the host container and the application.
Application frameworks inevitably have "rough edges" where a general deploy script cannot prepare an application for deployment. Application developers are forced to smooth the edges of the framework through bloated deployment systems, PaaS providers, or manual build scripts.
Bulk provides "packing", application plugins, for many common frameworks. These plugins are availabel through the chosen dependency management system for that framework. Packing plugins become part of your app, promoting the use of your deployment system in development, test, and continuous integration.
Packing scripts provide a uniform interface to Bulk without burdening the deployment system with knowledge about every possible framework. Packing can be developed and maintained in a familiar language to application developers.
Add this line to your application's Gemfile:
gem 'bulk'
And then execute:
$ bundle
Or install it yourself as:
$ gem install bulk
git checkout -b my-new-feature)git commit -am 'Add some feature')git push origin my-new-feature)FAQs
Unknown package
We found that bulk 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.