<indirect>
yopp: copying vendor/bundle is not supported and may break easily
<indirect>
copy vendor/cache and run bundle install on the target machine instead
<yopp>
huh
<yopp>
so there no way to get portable bundle?
<indirect>
the files in vendor/bundle will only work with the exact same ABI, for Ruby, libxml, libpg, etc etc
<indirect>
if any of those change, everything will stop working
<indirect>
there is no such thing; installed gems contain dynamically linked binaries
<yopp>
in case of jruby, they are mostly not :)
<indirect>
you can port the bundle with the .gem files and then install them
<indirect>
oh, sure :)
<indirect>
I mean, feel free to try it!
<yopp>
I've tried
<indirect>
but if it doesn't work, we don't support it :)
<indirect>
the supported option is to copy around vendor/cache and run bundle install
<yopp>
uh.
<indirect>
?
<yopp>
in case if jar, I don't think that bundle install will work
<yopp>
because bundler depends on cwd, and cwd is not the same as the path where bundle is lockaed
<yopp>
•located
<indirect>
Bundler does not depend on cwd
<indirect>
I'm confused
<yopp>
um.
<yopp>
It's 3 in the morning here, but seems like I have like alot of use cases where either I'm doing something wrong, or bundler can't handle that :)
<indirect>
I see :)
<indirect>
if you set BUNDLE_GEMFILE, cwd doesn't matter
<yopp>
mmmm
<yopp>
env vars
<yopp>
crap. and bundle exec sets that, right?
<yopp>
because one of my use cases is to system('bundle install') from ruby started with bundle exec :)
huoxito has joined #bundler
huoxito_ has joined #bundler
Pupeno has joined #bundler
huoxito has quit [Ping timeout: 265 seconds]
hagabaka has joined #bundler
Pupeno has quit [Ping timeout: 250 seconds]
axl_ has joined #bundler
axl_ has quit [Client Quit]
<mstred>
@indirect hey... talking about cwd, is there a way to install Gemfile-specific deps into cwd (without setting this as default for future installs)?
<indirect>
mstred: path followed by bundle config --delete path
<indirect>
but then Bundler won't be able to find them
<indirect>
so I don't know what that buys you
<indirect>
mstred: actually, come to think of it, I think `BUNDLE_PATH=foo bundle install`will not save the path
houhoulis has joined #bundler
<mstred>
@indirect something like default behavior on node's "npm install"
<indirect>
mstred: you’ll have to be more specific, sorry
<mstred>
@indirect actually, i see that bundler behaves like using "npm install -g"
<indirect>
npm and bundler are fundamentally different in a lot of ways, what specifically are you asking about?
<mstred>
@indirect installing deps in cwd for each project i could use
<indirect>
mstred: that _is_ bundle install —path
<indirect>
I personally use `bundle install —path .bundle`
<indirect>
why do you want to remove the path config? that just means that you can’t use those deps because Bundler doesn’t know where to look for them anymore
<mstred>
@indirect for instance, I have a Project A with its Gemfile with specific deps (and versions)
<mstred>
@indirect also... I have a Project B, another Gemfile... different deps (and/or versions from deps)
<mstred>
@indirect if I use --path flag for Project A, this will be set as default path... right?
<mstred>
@indirect so if I run "bundle install" with no flags for Project B, this would install its gems into Project A's directory?
<indirect>
no
<indirect>
—path is saved on a per-project basis
<indirect>
one per Gemfile
<indirect>
so I run `bundle install —path` in every project I use
<indirect>
and every project contains only the gems needed for that project in the directory I specified
<mstred>
@indirect hm... gotta try it once more
<mstred>
@indirect thank you!
<indirect>
np
<mstred>
@indirect one more thing, hehe... is there a way to set this "path" config thru Gemfile spec?
<indirect>
mstred: no
<indirect>
it is not shared by different users
<mstred>
@indirect this would be awesome...
<indirect>
it is up to the individual user who is installing the gemfile where they want to put their gems
<indirect>
Gemfiles are not allowed to have an opinion about it
<indirect>
if you always want to install to the same place, maybe create a shell alias?
<indirect>
I use “alias bip="bundle install --path"
<mstred>
@indirect ok... I understand, this would be open to vulns
djbkd has quit [Remote host closed the connection]
<mstred>
@indirect I guess I could do it over a rake task... this seems to be ok, right?
valarissa has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<indirect>
mstred: sure, except what version of rake will you use? ^_^
<mstred>
@indirect I'm not declaring it on Gemfile... only "gem 'rake'"
<mstred>
@indirect latest, I guess
<indirect>
oh, I just mean… how do you install rake to run bundler to install rake?
<indirect>
if you make a rake task that runs bundler, when you first check out the project, you won’t have rake yet...
<mstred>
@indirect oh, that's right
<mstred>
@indirect sorry, I'm still learning... hehe
<indirect>
:)
<mstred>
@indirect anyway, I just installed rake to system previously
<mstred>
@indirect but that workflow doesn't seem to be right to a clean install
<mstred>
@indirect I just wanted to make sure anyone contributing to the project would be using the same deps (and versions)
<mstred>
@indirect this actually relates to an issue I have with 'github-pages' gem
<indirect>
mstred: they always will, bundler requires it
<mstred>
@indirect they still use kramdown on v1.5.0
<indirect>
you don’t need a rake task that runs bundle install to ensure that
<mstred>
@indirect if I run "gem update", this will bump it to 1.8.0 (current version)
<mstred>
@indirect if I run tests in a project with the 'github-pages' gem (which uses kramdown 1.5.0), it will fail
<indirect>
mstred: you need to run the tests via `bundle exec <run the tests>`
<indirect>
so that you will get kramdown 1.5
<mstred>
@indirect in another project, I use kramdown with no version declared and it works fine
<indirect>
mstred: how is that related to this problem?
<mstred>
@indirect I was thinking about installing 'github-pages' related deps into project's cwd
<mstred>
@indirect so I wouldn't have dependency-related issues
<indirect>
do this:
<indirect>
wait
<indirect>
actually
<indirect>
does github-pages have a Gemfile?
<indirect>
if it does, you can just use `bundle exec`
<indirect>
and it will make your dependency issues go away
<mstred>
@indirect with no args, right?
<mstred>
@indirect it doesn't work
<indirect>
mstred: no, you have to use bundle exec to run all your commands
<indirect>
tests, servers, whatever
<mstred>
ok
<indirect>
bundle exec sets up gems so that you get the correct versions
<indirect>
I have to take off, but the documentation at bundler.io will probably help you
<mstred>
@indirect all right, thank you very much!
<mstred>
@indirect you're awesome
Pupeno has joined #bundler
Pupeno has quit [Ping timeout: 240 seconds]
robbyoconnor has quit [Ping timeout: 265 seconds]
robbyoconnor has joined #bundler
mstred has quit [Quit: Page closed]
djbkd has joined #bundler
bf4_ has quit [Ping timeout: 246 seconds]
djbkd has quit [Ping timeout: 250 seconds]
bf4 has joined #bundler
huoxito_ has quit [Remote host closed the connection]
bf4 has quit [Ping timeout: 240 seconds]
bf4 has joined #bundler
houhoulis has quit [Remote host closed the connection]
Pupeno has joined #bundler
Pupeno has quit [Quit: Leaving...]
djbkd has joined #bundler
habitullence has joined #bundler
habitullence has quit [Client Quit]
habitullence has joined #bundler
habitullence has quit [Quit: habitullence]
habitullence has joined #bundler
djbkd has quit [Remote host closed the connection]
Pupeno has joined #bundler
djbkd has joined #bundler
djbkd has quit [Ping timeout: 272 seconds]
<yopp>
indirect, ping me when you'll be there
pheuko has joined #bundler
chouhoulis has quit [Remote host closed the connection]
chouhoulis has joined #bundler
chouhoulis has quit [Ping timeout: 240 seconds]
huoxito has joined #bundler
chouhoulis has joined #bundler
dstarh has joined #bundler
chouhoulis has quit [Remote host closed the connection]
chouhoulis has joined #bundler
valarissa has joined #bundler
huoxito_ has joined #bundler
huoxito has quit [Ping timeout: 264 seconds]
r0bby_ has joined #bundler
ntucker has quit [Ping timeout: 244 seconds]
robbyoconnor has quit [Ping timeout: 244 seconds]
ntucker has joined #bundler
ineb has joined #bundler
<ineb>
i have ruby code that modifies the $LOAD_PATH and then loads code from another application, that has its own gemfile
<ineb>
i include that other app via 'require_relative', however, the require 'bundler/setup' does not seem to alter the $LOAD_PATH any more
<ineb>
and therefore the included app fails, because the dependencies are not discovered
djbkd has joined #bundler
maletor has joined #bundler
habitullence has quit [Quit: habitullence]
djbkd has quit [Ping timeout: 244 seconds]
<ineb>
could it be that require 'bundler/setup'
<ineb>
needs to be called on the very beginning? and later calls does not work
<ineb>
guess i have to check the source
pheuko has quit [Quit: pheuko]
djbkd has joined #bundler
djbkd has quit [Remote host closed the connection]
Pupeno_ has joined #bundler
Pupeno has quit [Ping timeout: 265 seconds]
djbkd has joined #bundler
ac has joined #bundler
<ac>
ohai
<ac>
i haz question about bundler and ruby in general that i dont really seem to have an answer to from various deployment tool docs
<ac>
chef such
<ac>
when i do bundler install, it fetches data from Fetching source index from https://rubygems.org/
<ac>
then downloads gems from there
<ac>
is there anyway to avoid that and install gems from a local source?
<ac>
ie pull all the gems then ship an application with them to be installed
<ac>
(including any system dependancies, like openssl or other libs)