To install gems Bundler needs to be able to talk to https://api.rubygems.org.

If you are behind a proxy you can use the https_proxy environment variable:

https_proxy=http://myproxy:123 bundle install

Note that if there is no https_proxy env variable, Bundler will also look for a http_proxy env variable.

With Capistrano

Ideally the server you're deploying on exports an https_proxy variable for all shells.

If you don't have control over the server setup, you can also add this to your Capistrano config:

set :bundle_env_variables, { 'https_proxy' => 'http://myproxy:123' }

Henning Koch

makandra.com

Say thanks5

Last edit

Almost 6 years ago

Henning Koch

Keywords

rubygems

License

Source code in this card is licensed under the MIT License.

Async control flow in JavaScript: Promises, Microtasks, async/await

Slides for Henning's talk on Sep 21st 2017.

Understanding sync vs. async control flow

Talking to synchronous (or "blocking") API

print('script start')
html = get('/foo')
print(html)
print('s...

Delivering Carrierwave attachments to authorized users only

Preparation

To attach files to your records, you will need a new database column representing the filename of the file. To do this, add a new migration (rails g migration <name>) with the following content:

class AddAttachmentToNotes...

Posted by Henning Koch to makandra dev (2016-02-01 09:47)

Bundler: Install gems behind a proxy

With Capistrano

Related cards:

Understanding sync vs. async control flow

Talking to synchronous (or "blocking") API

Summary

Introduction

Preparation