airbrussh | Airbrussh pretties up your SSHKit and Capistrano output

this is my first attempt to deploy a Rails app using Capistrano. I am following the tutorial at https://ogdenstudios.xyz/blog/how-do-i-deploy-a-rails-6-app-to-amazon-ec-2/ to deploy to an AWS EC2 instance. My app is on Rails 6 and runs smoothly on localhost. I followed the tutorial but I am stock in the final step, when i run cap production deploy y get the following error:

I am using rails "v6.0.2.2". I am following a gorails tutorial to deploy a rails 6 app to a digital ocean droplet using the following gems. Also note I am not using his app from the tutorial I made my own.

• gem 'capistrano', '~> 3.11'
• gem 'capistrano-rails', '~> 1.4'
• gem 'capistrano-passenger', '~> 0.2.0'
• gem 'capistrano-rbenv', '~> 2.1', '>= 2.1.4'

When I run cap production deploy it hangs up on,

I'm trying to deploy a Rails 6 app with Capistrano + Nginx + Puma. In the past(Rail 4 in that case) I used this tutorial https://www.digitalocean.com/community/tutorials/deploying-a-rails-app-on-ubuntu-14-04-with-capistrano-nginx-and-puma and it worked fine.

However, when I try to run cap production deploy:initial(or without the initial namespace) I receive the following error: The deploy has failed with an error: Exception while executing on host 31.220.51.222: Exception while executing on host 31.220.51.222: corrupted hmac detected ** Invoke deploy:failed (first_time) ** Execute deploy:failed

So I'm not sure if it is a problem with NET::SSH and where it comes from, or if it is a problem that have nothing to do with this message.

Following is the last lines of capistrano.log with the -t option enabled.

I'm getting a 'Connection Refused' error when attempting to deploy my rails app. This is the message I get from /var/log/nginx/error.log

I have a long-term-stable Rails 5.1 app deployed to Ubuntu 18.04.3 using MySQL.

I came to deploy a mundane update yesterday, and for some reason I've started getting the error,

LoadError: Error loading the 'mysql2' Active Record adapter. Missing a gem it depends on? mysql2 is not part of the bundle. Add it to your Gemfile.

Of course, the gem is already in my Gemfile (and Gemfile.lock), and its installed on the deployment machine. I had made some unrelated Gemfile changes (switched to mini_racer and added bcrypt), which required me to update to Bundler 2.0.2 over 2.0.1, but that's it.

Things I've tried:

1. I've tried going back to the code base before any gem changes and switched back to bundler 2.0.1, but I still hit the same problem on deployment - now it's broken, it seems to be staying broken.

2. I tried deploying to a entirely independent server I have set up (still on Ubuntu 18.04) and now see the same problem.

3. I found these apparent duplicate questions, and there the fix was to go back to an earlier version of the mysql2 gem (I tried 0.3.20 as I saw mention that 0.3.21 doesn't work), but that doesn't fix it in my case. I've tried uninstalling all other versions on the server side.

4. The comments around the above linked question say this will be fixed in Rails 5 (I was already using 5.1) but I went through the exercise of updating my Rails app to 5.2 to get the very latest gems, and specified mysql 0.5.2 to see if I could leap frog the versions of mysql2 with the issue, but still I hit the same problem.

My 'current' Gemfile.lock file is pasted below, but this issue started with Rails 5.1.7 and Bundler 2.0.1 and I've tried all permutations of mysql2 0.3.18, 0.3.20 and 0.5.2.

Without a fix I am unable to deploy a Rails app update, so any suggestions as to how to overcome this deployment problem much appreciated.

I have a DigitalOcean Droplet with a Rails application in which I wanted to automate deploys via Pipelines and Capistrano.

This is my Capfile:

I am trying to migrate from Rails 4.2 to Rails 5.0 (running on ruby 2.3) (see plan here https://stackoverflow.com/a/38443616/7374136)

The plan is to:

1. Update the rails gem and all dependencies.
2. Run tests (covering almost our whole code base) for depreciations and fix them.
3. Run rake rails:update to update Rails
4. Adapt the configuration, application classes, breaking changes, ...

Nevertheless, I am blocked at the first step already, updating the rails gem and dependencies. gem 'rails', '4.2.5' -> gem 'rails', '~> 5.0' running: bundle update rails.

I faced multiple dependencies issues, which I fixed by looking for any dependencies that ultimately require rails to be less than 5, and see if those can be updated. Running:

I install Ruby On Rails on Ubuntu 18.04 using RVM. ruby -v : 2.4.0 rails -v : 5.1.3

I try to run "bundle install" command, I getting below error. please provide me best solution for this.

Could not verify the SSL certificate for https://rails-assets.org/. There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see 'bit.ly/ruby-ssl'. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Gemfile

I have been deploying with Capistrano for over a year and able to rollback and now all of a sudden I cannot rollback saying it cannot find the rake asset file

Capistrano Rollback is failing complaining that it cannot find the rake asset manifest which I validated is not there. What creates this and why would it just stop being created?

I have been pulling my hair out for days over this and am at a point to figure out how to hack out that portion of the rollback and manually recompiling the assets.