bundle lock
Generate a lockfile for your dependencies
Options
| Name | Description |
|---|---|
--update <arg> | Ignores the existing lockfile |
--local | Do not attempt to connect to rubygems.org |
--print | Prints the lockfile to STDOUT instead of writing to the file system |
--lockfile <path> | The path where the lockfile should be written to |
--full-index | Fall back to using the single-file index of all gems |
--add-platform | Add a new platform to the lockfile, re-resolving for the addi- tion of that platform |
--remove-platform | Remove a platform from the lockfile |
--patch | If updating, prefer updating only to next patch version |
--minor | If updating, prefer updating only to next minor version |
--major | If updating, prefer updating to next major version (default) |
--strict | If updating, do not allow any gem to be updated past latest --patch | --minor | --major |
--conservative | If updating, use bundle install conservative update behavior and do not allow shared dependencies to be updated |