Gem process is complicated about genesis HOT 3 CLOSED

1. We don't tell the user to create the gems anywhere in the testenv
   README
2. This seems overly complicated to me. Can't we publish the gems on
   rubygems and install them in the testenv from there? And then if we or
   other users want customized gems publish them to an internal repo. Or at
   least skip the step of going through the web app and install them directly
   from /genesis?

(1) is definitely a problem
(2) I agree. My intent was to have the testenv spin up a gemserver, but I
was having trouble getting that to work, specifically installing the gems
in the testenv, so went to the current method.

I think we can publish the gems on rubygems once this goes public since the
gems should not have any tumblr-isms in them. The caveat is that they also
don't have documentation and IMO are pretty ugly because of that.

The testenv web app is just a way to export (read that make available) the
files. If the bootbox gemserver works we can/should use that instead.
Thanks.
Roy

On Tue, Jan 20, 2015 at 9:12 AM, Felix Aronsson [email protected]
wrote:

When trying to set up Genesis from scratch, i run into and issue where the
genesis bootloader cannot load retryingfetcher or promptcli. LoadError:
cannot load such file -- 'retryingfetcher'
(@maddalab https://github.com/maddalab: Is this what you saw as well?)

At first I thought it was DNS messing up the installation of this gem
somehow, but both of these are installed when creating the image with
create-image.sh. See genesis.ks L221
https://github.com/tumblr/genesis/blob/master/bootcd/genesis.ks#L221
and genesis.ks L250
https://github.com/tumblr/genesis/blob/master/bootcd/genesis.ks#L250.

So, in the testenv, kickstart fetches the gems through the web app (from
static files in /genesis/src/*/
https://github.com/tumblr/genesis/blob/master/testenv/bootbox/web/genesis.rb#L19),
stores them in /root/repo/gems and then installs them from there. The
problems i see here are:

1. We don't tell the user to create the gems anywhere in the testenv
   README
2. This seems overly complicated to me. Can't we publish the gems on
   rubygems and install them in the testenv from there? And then if we or
   other users want customized gems publish them to an internal repo. Or at
   least skip the step of going through the web app and install them directly
   from /genesis?

I'll get a branch going with some README updates and leave the floor open
for discussion about the process.

@roymarantz https://github.com/roymarantz @maddalab
https://github.com/maddalab @byxorna https://github.com/byxorna

—
Reply to this email directly or view it on GitHub
#15.

from genesis.

Cool, thanks @roymarantz, seems like we're on the same page. With (1) fixed i think we're in a decent state, but let me know if i can work on something with the gem setup.

from genesis.

@defect if you want to fix it, that would be cool. I suspect this might be due to bootbox and genesis being different based on different versions of the "OS".

from genesis.