We regularly need to connect to the server in order to e.g. access the production console. Guessing the Capistrano deploy user and then again guessing the right directory on the server is awkward, so we wrote a script that parses config/deploy and gives you the handy command shell-for.

Run it from any project directory like this, passing a Capistrano multistage deployment target:

shell-for staging

Now it also supports commands to be remotely executed before loading the bash. Use --no-bash to only execute the command and load no bash.

shell-for staging --no-bash top

This script is part of our geordi gem on github Show archive.org snapshot .

Dominik Schöler

makandra.de

Say thanks2

Last edit

Over 11 years ago

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...

How to fix "Too many authentic authentication failures" with SSH and/or Capistrano

You are getting when connecting via SSH or deploying with Capistrano (which uses SSH):

Too many authentication failures for username

This is caused by having too many SSH keys added to your keyring or ssh-agent. Your ssh-agent will throw all...

Posted by Dominik Schöler to makandra dev (2011-05-13 15:42)

Script to open an SSH shell to a Capistrano deployment target

Related cards:

Understanding sync vs. async control flow

Talking to synchronous (or "blocking") API

Summary

Introduction

Preparation