Dockerize ytrello

[teclator]

Just an idea, the ytrello credentials could be copied also to /root/.config/ytrello-creds.yml instead of using environment variables.

Copy your osc credentials as oscrc

cp ~/.oscrc /ytrello_path/oscrc

Build ytrello

docker build -t ytrello .

Add ytrello as an alias

# Add to your .bashrc a ytrello alias and define the environment trello credentials
export TRELLO_DEVELOPER_PUBLIC_KEY=ffffffffffffffffffffffffffffffff
export TRELLO_MEMBER_TOKEN=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
alias ytrello="docker run -ti -e TRELLO_DEVELOPER_PUBLIC_KEY=$TRELLO_DEVELOPER_PUBLIC_KEY -e TRELLO_MEMBER_TOKEN=$TRELLO_MEMBER_TOKEN ytrello"

Start using it

ytrello ./check
ytrello ./create 1065...

[mvidner]

OK the deployment stage is something which I haven't really figured out, and this is another improvement to it.
Can you please move the docs in the PR description to the README (or perhaps a separate README-docker?)

[mvidner]

Is this necessary for the dockerization? Because removing this would mean that the previous deployment method gets broken.

[teclator]

The main problem is that it assumes the bundler_dir for you and force the install if not present while it should just a

require 'rubygems'
require 'bundler/setup'

letting to the user the decision about his bundle path, config and so on.

http://bundler.io/v1.12/bundler_setup.html#bundlersetup

We could modify the Dockerfile to explicitly use the .vendor dir avoiding the remove of this chunk of code but not sure if it is the recommended way of bundle use. I was surprised why always that I launched the commands after a build it was installing again all the gems... took me sometime to realize that it was because the code force you to install the gems in a specific path.

[teclator]

BTW, I will just remove the global path and it will work fine again not having to remove anything from previous code by now.

[mvidner]

Well, I can still make it fail if I first run ytrello in my checkout and THEN build the image. And it seems you cannot build it from a fresh checkout because it expects a Gemfile.lock. Can you please make it work with a fresh checkout?

[mvidner]

Maybe we should simply commit the Gemfile.lock

[teclator]

@mvidner ups that's true, I overlooked that the Gemfile.lock was git ignored. So yes, I would add it to git or use at least add one for being copy into the container as Gemfile.lock

In the past it was usually ignored, but nowadays, being an application and not a library it usually makes sense to have the gems versions that we are sure work fine locked.

[teclator]

@mvidner last changes summary:

I was using an old Gemfile.lock and also the Dockerfile was based on ruby 2.2. I have adapted it using ruby 2.4 instead.

If you prefer, we can omit the Gemfile.lock and just remove the copy from the Dockerfile.

[mvidner]

Now I synced Gemfile and Gemfile.lock, but @lslezak 's bundler setup no longer works as nicely. You have to use

$ bundler.ruby2.4 install
$ ruby.ruby2.4 $ytrello_tool

Huh, I hope I can find a way out of this mess.

[teclator]

That is exactly the problem about having multiple versions and what I tried to solve using docker. BTW, bicho was dropping support for ruby < 2.3 dmacvicar/bicho@8f23785

[mvidner]

OK, I think this still is an improvement, and if we need to touch this area again, let's make a regular gem out of it, and put it in OBS to get nicely versioned executables.