1. 31 Mar, 2021 2 commits
  2. 30 Mar, 2021 4 commits
  3. 09 Mar, 2021 5 commits
  4. 08 Mar, 2021 2 commits
    • Nicolas Bouilleaud's avatar
      Merge branch 'fix-active-storage-missing-config' into 'main' · 3f6977c6
      Nicolas Bouilleaud authored
      Add missing config/storage.yml
      
      See merge request !107
      3f6977c6
    • Nicolas Bouilleaud's avatar
      Add missing config/storage.yml · 49bea638
      Nicolas Bouilleaud authored
      In production (only), rails complain if that file is missing, even if we don’t use ActiveStorage, and even if it doesn’t contain configuration for production.
      
      The stack trace looks like this.
      ```
      2021-03-08T14:53:29.070Z: [2162] ! Unable to load application: RuntimeError: Couldn't find Active Storage configuration in /home/bas/app_8a8c9635-034e-4b28-a10f-e196ea3c28fd/config/storage.yml
      2021-03-08T14:53:29.070Z: bundler: failed to load command: puma (/home/bas/app_8a8c9635-034e-4b28-a10f-e196ea3c28fd/vendor/bundle/ruby/2.7.0/bin/puma)
      2021-03-08T14:53:29.070Z: RuntimeError: Couldn't find Active Storage configuration in /home/bas/app_8a8c9635-034e-4b28-a10f-e196ea3c28fd/config/storage.yml
      ```
      
      The contents of the added file is just the template from the rails 6 migration tool. I think I ignored it on purpose when I did the migration.
      
      I had a lot of trouble to debug it on Clever Cloud, because the ruby stack trace didn’t appear in the logs, and only the mention that the “Early termination of worker”, supposedly because of high RAM usage.
      
      Or I could have just started `RAILS_ENV=production rails s` locally to see the error.
      49bea638
  5. 20 Jan, 2021 1 commit
  6. 18 Jan, 2021 5 commits
  7. 13 Jan, 2021 7 commits
  8. 11 Dec, 2020 4 commits
  9. 07 Dec, 2020 4 commits
  10. 04 Dec, 2020 6 commits