- Your deployment system MUST have the bundler gem installed
- `bundle install –deployment` requires a Gemfile.lock, so `bundle install [--without]` needs to be run first.
- `bundle install` will make a Gemfile.lock, even it doesn’t install any gems via `–without`, so if you don’t have access to install gems you don’t have to.
- `bundle install –deployment` will bundle the gems t0 vendor/bundle AND freeze the app in .bundle/config.
- If you do `bundle install –without` to make a Gemfile.lock on the same system you want t0 do `bundle install –deployment` you will have to trash .bundle in-between.
- If you want your bundle in your repository, you still need to run `bundle install –deployment` on other servers or also add .bundle, even though it is intended to be server specific, just so long as you have a .bundle/config with BUNDLE_FROZEN: 1.
- If you add .bundle to your repository you can get by without the bundle executable in your deployment server, but not the bundler gem.
- If your having trouble, trash .bundle, but make sure your deployment server has a .bundle/config with BUNDLE_FROZEN: 1 when you’re done bundling.
- 2010
- 12/16
- CATEGORY
- Uncategorized
February 2012
| M |
T |
W |
T |
F |
S |
S |
| « Dec |
|
|
| | 1 | 2 | 3 | 4 | 5 |
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 |
|