' [ E 2022-06-22 15:04:13.2231 21017/T9t age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/deploy/cartazzi_marketing/current: The application encountered the following error: You have already activated strscan 3.0.1, but your Gemfile requires strscan 3.0.3. Since strscan is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports strscan as a default gem. (Gem::LoadError) Error ID: 9a03b9ce Error details saved to: /tmp/passenger-error-pO6ZTu.html The normal googling suggested things like: Update strscan on the host system Mess with Gemfile Mess with Gemfile.lock Add a Passenger level configuration var for bundler I'd give citations for these but Chrome just crashed and it is closing in on 4 am and the weariness in my bones doesn't allow me to r ## Using SSL in HatchBox with AWS Route 53 DevFeed: [Using SSL in HatchBox with AWS Route 53]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-23T07:01:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Amazon Route 53](), [Rails](), [SSL](), [Amazon Web Services](), [AWS IAM](), [Deployment](), [JSON]() Tags: [aws](), [cartazzi](), [credentials](), [deployment](), [hatchbox](), [iam](), [json](), [rails](), [route53](), [ssl]() ### AI overview A practical guide to configuring wildcard SSL in HatchBox with AWS Route 53. It explains the required Route 53 setup, IAM user and JSON policy configuration, credential handling, and the addition of route53:ListResourceRecordSets after an incomplete policy caused validation problems. ### Source excerpt HatchBox continues to be my favorite tool for Rails deployment hands down. And this includes Dockarno - my own Bash based Docker deployment tool. When something you pay for replaces something you wrote yourself, that's a sign of its very, very strong goodness. I just used HatchBox to support SSL wildcard deployment for something I'm building and the process was a tad bit tricky so I thought I'd write it up. HatchBox has excellent built in SSL support using Let's Encrypt but when you use wildcard SSL, you get asked for the Route 53 Key and the Route 53 secret. Here's how you get those: On AWS, in Route 53 In Route 53, make sure you have *.domain.extension defined to allow it to be wildcard. On AWS, in IAM In the IAM console, you need to: Add a user Add that user to a group Add a JSON policy document Here is the JSON policy that you need to add: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "route53:GetChange", "Resource": "arn:aws:route53:::change/*" }, { "Effect": "Allow", "Action": "route53:ChangeResourceRecordSets", "Resource": "arn:aws:route53:::hostedzone/*" }, { "Effect": "Allow", "Action": "route53:ListHostedZonesByName", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListHostedZones", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListResourceRecordSets", "Resource": "*" } ] } After you've added that user then you will be prompted with the normal AWS access key / secret key. Save the credentials and then add them to HatchBox. HatchBox will then got thru an API session with AWS and validate the key. My Experience and Chris's Brilliant Work I started from documentation I found online (see below) that turned out to be incomplete. When I examined the HatchBox log for the transaction, I saw this: -----> Connecting to SOMETHING3-lb (138.68.227.244 port 22) as root Uploaded /etc/logrotate.d/acme.sh Executing 'curl https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh | sh -s -- --install-online' % ## Rails 7 Madness: No such middleware to insert before: ActionDispatch::Static DevFeed: [Rails 7 Madness: No such middleware to insert before: ActionDispatch::Static]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-02T04:22:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Vite](), [Ruby](), [npm packages]() Tags: [deploy](), [errors](), [hatchbox](), [logging](), [npm-packages](), [rails](), [rake](), [troubleshooting](), [vite]() ### AI overview A troubleshooting account of a Rails 7 deployment error reporting that no middleware could be inserted before ActionDispatch::Static. The author reproduced the issue with Rails commands, added the smart_assets gem, and then encountered a different deployment failure indicating that the Vite binary was unavailable. ### Source excerpt In tonight's category of "Crazy Rails Errors that Even I haven't hit", I was deploying a new app via HatchBox and I hit this one: No such middleware to insert before: ActionDispatch::Static /home/deploy/Cartazzi/shared/bundle/ruby/3.1.0/gems/actionpack-7.0.2.2/lib/action_dispatch/middleware/stack.rb:174:in `assert_index' When I dug into the underlying failure there was this bit of code: def assert_index(index, where) i = index.is_a?(Integer) ? index : index_of(index) raise "No such middleware to insert #{where}: #{index.inspect}" unless i i end I did the obligatory googling only to find nothing in the past year and absolutely nothing related to Rails 7. I was able to replicate this by logging in with either: bundle exec rake middleware or RAILS_ENV=production bundle exec rake assets:precompile After stumbling around a bit - this was post midnight late night code fu - I thoguht to myself: What if the issue is that it is looking for middleware and it can't find any? One of the previous googles from 2015 or so said that if you have this issue then remove the font_assets gem (I didn't have it but omitted that part of the research above). What I did was look for asset pipeline middleware and I found the smart_assets gem which I dropped into Gemfile: gem 'smart_assets' A quick bundle install and I ended up with a failing deploy ... but a different failure: Building with Vite rake aborted! ViteRuby::MissingExecutableError: The vite binary is not available. Have you installed the npm packages? Visit the Troubleshooting guide for more information: https://vite-ruby.netlify.app/guide/troubleshooting.html#troubleshooting And that, in modern computing, alas, is progress. ## Specifying Ruby Version for HatchBox Deployment DevFeed: [Specifying Ruby Version for HatchBox Deployment]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-05-31T11:13:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Ruby](), [Deployment]() Tags: [deployment](), [errors](), [hatchbox](), [ruby](), [rvm]() ### AI overview This article explains how to resolve a Ruby version conflict during Hatchbox deployment by keeping the Ruby version in the Gemfile synchronized with the version in .ruby-version. The author reports that synchronizing both files to Ruby 2.6.2 fixed the issue. ### Source excerpt I recently had the situation where an application that I deployed to Hatchbox failed with a Ruby version conflict: -----> Installing gems... /home/deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated Your Gemfile lists the gem capybara (>= 0) more than once. You should probably keep only one of them. Remove any duplicate entries and specify the gem only once (per group). While it's not a problem now, it could cause errors if you change the version of one of them later. Your Ruby version is 2.5.1, but your Gemfile specified 2.6.2 I dug into the (excellent) online help for Hatchbox and found that you can specify your Ruby version with either the Gemfile or the .ruby-version file. These files, however, serve different functions: Gemfile - tells your application what to use .ruby-version - tells RVM to switch the ruby version on change into the directory In my case I had both and they were different. Synchronizing them both to 2.6.2 fixed the issue entirely. ## Deploying to HatchBox with Rails 5.x DevFeed: [Deploying to HatchBox with Rails 5.x]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-14T13:22:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Environment Variables](), [PostgreSQL]() Tags: [deploy](), [environment-variables](), [hatchbox](), [postgresql](), [rails]() ### AI overview A tutorial on deploying a Rails 5.x application to HatchBox. It covers upgrading to Rails 5.2 when needed, configuring an existing PostgreSQL database and environment variables, creating Rails credentials, setting up a domain and Let's Encrypt SSL, and verifying the deployment. ### Source excerpt I just got a database less home page for a future SAAS app deployed via HatchBox under Rails 5.x and I thought the differences were significant enough that I should document it. HatchBox is the best tool I've ever found for Rails deploys but knowing all the steps to follow is key. elixi: Other than the Rails 5.2 upgrade step, there aren't many differences between this and Rails 6 but it has been long enough since I've done this that writing it down felt right. 1. Upgrade Rails to "5.2.x" if You Don't Have rails credentials:edit If your Rails 5 version is old enough that you get this crap: ❯ rails credentials:edit rails aborted! Don't know how to build task 'credentials:edit' (see --tasks) Here's the line you want to put into your Gemfile: gem 'rails', '~> 5.2' Once you change your Rails version, you want to use: bundle update to upgrade your Rails installation. 2. There is No True Database Less Deploy in HatchBox HatchBox is designed to work with a database (which is also the Rails default) because it calls database create and database migrate as part of the deploy. The trick here is to use an existing database and set your env variables and database.yml to allow for this Here's how to set up your database.yml file: production: adapter: postgresql url: <%= ENV['DATABASE_URL'] %> encoding: utf8 pool: 50 Your env variables are described in the section below. As long as you don't have migrations or database tables as part of your app, you can use any DATABASE_URL value (you set this below under environment variables; I just copied one from a different application). 4. Run rails credentials:edit The command: rails credentials:edit creates the Rails master key and secret key base that you need. You want to save your master key and secret key base because you need both in the env variables section. 5. HatchBox Setup You want to: Add your app to github or another supported version control system and note the username/repo_name pairing Create a new app Choose the cluster Ad ## Having Hatchbox Redirect All http Sites it Manages to https DevFeed: [Having Hatchbox Redirect All http Sites it Manages to https]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [nginx](), [SSL](), [HTTP](), [configuration](), [servers]() Tags: [can](), [code](), [configuration](), [deploy](), [hatchbox](), [http](), [https](), [nginx](), [request](), [server](), [ssl]() ### AI overview A guide for configuring Hatchbox and nginx in cluster mode so HTTP requests are redirected to HTTPS at the load balancer. It provides the nginx directive and the Hatchbox interface steps needed before deploying the change. ### Source excerpt When you are using hatchbox and SSL in cluster mode you end up with: a load balanced cluster that uses nginx as the load balancer and nginx on each web node This makes it hard to understand where the http to https redirect goes. The answer is that you need to but this on the load balancer and here's a code snippet: server_name _; return 301 https://$host$request_uri; This gets set as follows: Go into Hatchbox.io Go into your app. Go to Advanced. Select Nginx Configuration from the drop down menu Select the Load Balancer tab. Add these changes below the listen [::]:80; directive and then do a deploy. For reference, you can see linuxize. ## Deploying a Rails App Using HatchBox onto Google Cloud Platform DevFeed: [Deploying a Rails App Using HatchBox onto Google Cloud Platform]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-22T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Google Cloud Platform (GCP)](), [Deployment](), [PostgreSQL](), [Redis]() Tags: [config](), [deployment](), [git](), [google-cloud](), [google-cloud-platform](), [hatchbox](), [postgresql](), [rails](), [redis](), [ssh]() ### AI overview A practical guide to deploying a Rails application with HatchBox onto Google Cloud Platform. It covers creating a single-server cluster, configuring external Cloud SQL PostgreSQL and Redis services, connecting a Git repository, performing an initial HTTP deployment, and enabling SSL after assigning a domain. ### Source excerpt This blog post is a quickie where I document how I deployed CovidNearMe onto Google Cloud Platform or GCP using HatchBox.io. I need to start by giving a huge shout out to Tony Carnevale from Google who went above and beyond in providing outstanding support. Here are the stages. Stage 1: Create a Cluster Note: Even a single machine is considered a cluster. Go to HatchBox.io Login with your account. Click on Clusters and define a New Cluster. Name the cluster GCP Covid Near Me (or that's what I did). Select Somewhere Else as the hosting provider. Select the Everything on a Single Server option. If you are using the GCP Cloud SQL (postgresql) and GCP Redis then remove these options from the Roles list. Enter the IP address under public ip. Set the private IP to 127.0.0. There appears to be a bug where you can't provision the server unless a local redis installation is selected so add it back. Click provision the server and you will be given an SSH command to run as root on the box. You SSH in, do a sudo su, execute the command and exit out You click Test / Provision (I forget which) and your server will be flawlessly setup. Stage 2: Create an App on the Cluster Click on Apps. Click on Create a New App. Choose the cluster from the drop down list. Click on your git repo host. Set the name of your application (I like to include the name of the cluster with the app name since this app is already deployed to digital ocean). Enter the name of the repo (easily find this from .git/config in your Rails root directory). Set external host for the database if you are using Google's Cloud SQL. This means that you need to define a postgres configuration url. The format for this url is this: postgresql://user:password@databasehost.com/database. You simply need to replace user with your username, password with your password, databasehost.com with your database server and database with the name of the database. Define your Rails Master Key right away so you don't screw this up and have