Couldn't find Active Storage configuration in /home/user/mysite/config/storage.yml (RuntimeError) about decko

[ethn]

It's there, that's what threw me. But we run the smoke tests with every pull request, not every gem build. The code is all there and working in the git repository, but a directory was left out of the gem specification and therefore the code wasn't in the gem itself.

...which is a solid argument for adding separate smoke test for gem builds that only use gem code. Gem builds are far rarer - we push code almost daily but can go weeks between gem builds – but clearly we need this, especially for times when we're majorly reorganizing our code into gem dependencies, as we did with 0.11.0.

At any rate, thanks so much for your patience and help on this.

[ethn]

I saw this once with an existing site and was able to solve it by adding a blank storage.yml file. This must be a new requirement of one of the rails gems decko depends on, and you're right we should generate it.

Can you clarify one point for me: did you restart the server after adding the storage.yml file? I would have thought that would fix the problem, but if not I'll have to try to reproduce it and see what I can learn.

Thanks for bringing this to our attention!

[bertdeb]

Thanks again for the quick response.

I tried a completely blank storage.yml file (touch config/storage.yml)as well as the default starter storage.yml file from rubyonrails.org. No dice.

The server never ran, so it wasn't a matter of restarting it. Adding the storage.yml file (either blank or starter) allows the server to start, but it won't serve anything.

[ethn]

Got it, thanks. I'm wondering if the problem you're seeing now isn't actually related to the Active Storage issue. Are you seeing any in the log file (DECKROOT/log/ENVIRONMENT.log)?

This isn't terribly likely to solve the problem, but I would suggest using bundle exec decko server until we find the problem; that just eliminates one potential source of errors.

[bertdeb]

There is no DECKROOT/log/ENVIRONMENT.log. The only file in the log folder is production.log:

empty database
Started GET "/" for 127.0.0.1 at 2021-02-28 15:30:11 -0500
  
ActionController::RoutingError (No route matches [GET] "/"):
  
Started GET "/favicon.ico" for 127.0.0.1 at 2021-02-28 15:30:11 -0500
  
ActionController::RoutingError (No route matches [GET] "/favicon.ico"):
  
Started GET "/new" for 127.0.0.1 at 2021-02-28 15:30:22 -0500
  
ActionController::RoutingError (No route matches [GET] "/new"):

[ethn]

Yes, that's the log I meant. (I meant ENVIRONMENT as a variable; I wasn't sure you were running in the production environment).

I'm wondering about that first line, "empty database". Is it possible the seeding didn't work because of the Active Storage error?

Can you retry bundle exec decko seed and then restart the server?

[bertdeb]

I still get the same messages in production.log:

Started GET "/" for 127.0.0.1 at 2021-03-01 00:59:18 -0500
  
ActionController::RoutingError (No route matches [GET] "/"):
  
empty database

For what it's worth, here's the results of bundle exec decko seed:

bundle exec rake decko:seed
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
Database 'mysite_production' already exists
/var/lib/gems/2.7.0/gems/card-1.101.0/lib/cardio/mod/loader/set_loader.rb:13: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/var/lib/gems/2.7.0/gems/card-1.101.0/lib/cardio/mod/loader.rb:15: warning: The called method `initialize' is defined here
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/rake-12.3.0/lib/rake/application.rb:395: warning: deprecated Object#=~ is called on Proc; it always returns nil
/var/lib/gems/2.7.0/gems/card-1.101.0/lib/cardio/mod/loader/set_loader.rb:13: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/var/lib/gems/2.7.0/gems/card-1.101.0/lib/cardio/mod/loader.rb:15: warning: The called method `initialize' is defined here
not dropped
creating
loading schema
loading seed data
set symlink for assets
reset cache

[ethn]

Thanks for this.

Most of those warnings are noise. Ruby is making some changes in 3.0, and they're providing helpful warnings about them in 2.7. We'll address those in the next decko release.

I'm still a little confused about whether (a) the database is not getting seeded vs (b) it IS, but the server isn't finding it for some reason. I had thought it was (a), but those logs make me think it's (b).

I'm going to try to reproduce this, and I apologize for all the nuisance, but if you're willing to help me by doing two more things it would be a huge help.

1. confirm that the database is getting populated by going to mysql -u root mysite_production and then running select count(*) from cards. If it's empty, we've got a seeding problem, but based on the above I don't think it will be.
2. confirm that this isn't a caching problem by deleting everything in the deck's tmp directory. so you can, eg, run this from the deck's root dir: rm -r tmp/* and then restart the server.

Thanks so much for your patience and all the helpful details!!

[bertdeb]

select count(*) from cards;
+----------+
| count(*) |
+----------+
|      788 |
+----------+
1 row in set (0.04 sec)

Deleting everything in the tmp directory didn't change the outcome unfortunately. The server still doesn't serve anything.

I'm very happy to continue troubleshooting this with you.

[ethn]

Figured it out. Some critical files were missing from the decko gem. I just pushed version 0.11.1, and I was able to install, seed, start a server, and load a page. I think that may have also fixed the gem installation problem; I think the issue had something to do with introducing so many new gems (the mods) at once last time. And of course it adds a blank storage.yml file.

So update and let me know how it goes?

[bertdeb]

Yessir, that fixed it! Thanks!

Is it possible to add the creation of a new deck and starting the server to your build process? For newcomers, it helps when the getting started instructions just work ;-)