bible270 0.6.2 → 0.6.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c9baaae6c81c3923b1997672d8f13ff5edd97dba42c56f29ec86fee53c508512
-  data.tar.gz: c564d896cd9144cee1aa4321e0cc39aa77f3197fb7a6f599045053b0fb674204
+  metadata.gz: caccb805f18dbe442b8608eabaec724c594c0712aec78fa7a7cbc725ca7829aa
+  data.tar.gz: 2c571bf6ce6812776a464787cada63c732a9fe7a53cc70921f9a4192e7fa14b2
 SHA512:
-  metadata.gz: 0d2de30b25a9be283d994aef6db3c5743e7a3c112208eae6a3aa6b66cb45d893312cba18321f02dc240699ac774f13a9361cdb59b063c95e709cf934a0d602cc
-  data.tar.gz: cf3908da790617444a1ef1717c533912d1303ca6c5ca32624186262964a836997639940d578eea1c7f06c61ad3dd9d00f1e23401ce3cfb8e21d8f8084d62ba21
+  metadata.gz: c70d8f5ec550adf89c2952fd27ec2bc0eaf43ff8c6222d38677bb54ba56838a2af7de974448dbcbf9a1c45116169c90e4e5c2a56bbe72c898953fb3961edb72c
+  data.tar.gz: 2df597fecea51b44334239b82c88eb9e729c51ca11d947dbc41544364e6358f8c1f41cafab3a76c16cfe35f25872ee2bcac122f5c6fd11b2e0f3a8e248eb82e8

data/CHANGELOG.md

@@ -4,6 +4,19 @@ All notable changes to bible270. Format follows [Keep a Changelog](https://keepa
 this project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html), treating pre-1.0 minor
 bumps as the place breaking changes may land.
 
+## [0.6.3] — 2026-07-25
+
+### Fixed
+- **`db:migrate` failed with `ActiveRecord::DuplicateMigrationNameError`.** The engine appended its
+  own `db/migrate` to the host application's migration paths *and* exposed
+  `bible270:install:migrations`. Using the task — the documented install step — meant every
+  migration class was defined twice, once in the host's `db/migrate` and once in the gem. The engine
+  no longer touches the host's migration paths; copying via the task is the single supported path,
+  which also means the host owns the migrations and they appear in `schema.rb` normally.
+
+### Added
+- `spec.email` in the gemspec.
+
 ## [0.6.2] — 2026-07-24
 
 ### Changed
@@ -170,6 +183,7 @@ bumps as the place breaking changes may land.
 - The schedule is pure, deterministic Ruby — no rows are stored for the plan itself; the database
   holds only readers, check-offs, and comments.
 
+[0.6.3]: https://github.com/avonderluft/bible270/releases/tag/v0.6.3
 [0.6.2]: https://github.com/avonderluft/bible270/releases/tag/v0.6.2
 [0.6.1]: https://github.com/avonderluft/bible270/releases/tag/v0.6.1
 [0.6.0]: https://github.com/avonderluft/bible270/releases/tag/v0.6.0

data/README.md

@@ -31,7 +31,9 @@ nothing copyrighted is bundled). The database only holds **readers, check-offs,
 ## Requirements & compatibility
 
 - **Ruby** >= 3.0 (the gemspec's `required_ruby_version`). The plan logic is plain Ruby with
-  no C extensions and no dependency on any gem that Ruby 4.0 unbundled.
+  no C extensions and no dependency on any gem that Ruby 4.0 unbundled. Installs and loads under
+  Ruby 4.0.6; the test suite is exercised on 3.2 and passes with
+  `--enable-frozen-string-literal` forced.
 - **Ruby 4.0 notes.** Audited against the 4.0 breaking changes: the gem does not use `cgi`
   (removed from default gems in 4.0 — URL escaping goes through `URI.encode_www_form_component`
   instead, which is byte-identical to `CGI.escape`), `Set`/`SortedSet`, `Ractor`, `Net::HTTP`,
@@ -50,12 +52,22 @@ nothing copyrighted is bundled). The database only holds **readers, check-offs,
 Add to the host app's `Gemfile`:
 
 ```ruby
-gem "bible270", path: "vendor/gems/bible270"
-# or, once pushed to a git remote:
-# gem "bible270", git: "https://github.com/avonderluft/bible270.git", branch: "main"
+gem "bible270"
 ```
 
-Then:
+<details>
+<summary>Other sources (unreleased changes, local development)</summary>
+
+```ruby
+# straight from the repository
+gem "bible270", git: "https://github.com/avonderluft/bible270.git", branch: "main"
+
+# a local checkout you're editing
+gem "bible270", path: "../bible270"
+```
+</details>
+
+Then install, copy the migrations, and migrate:
 
 ```bash
 bundle install
@@ -63,14 +75,35 @@ bin/rails bible270:install:migrations
 bin/rails db:migrate
 ```
 
+`install:migrations` copies four migrations into your `db/migrate` (readers, check-offs, comments,
+sign-in tokens). They belong to your application from then on: they get your timestamps, appear in
+your `schema.rb`, and are yours to run, roll back, or edit. The engine does **not** add its own
+migration directory to your app's paths, so the copies are the only definitions in play.
+
 Mount it in `config/routes.rb`:
 
 ```ruby
 mount Bible270::Engine, at: "/reading-plan"
 ```
 
+Optionally generate the initializers (see [Authentication](#authentication)):
+
+```bash
+bin/rails generate bible270:install --mount-at=/reading-plan --providers=github
+```
+
 The plan is now live at `/reading-plan`.
 
+### Upgrading
+
+When a new version adds a migration, re-run the copy step — already-copied migrations are skipped:
+
+```bash
+bundle update bible270
+bin/rails bible270:install:migrations
+bin/rails db:migrate
+```
+
 ---
 
 ## Authentication
@@ -359,6 +392,54 @@ counts. That's ideal for a homelab/parish-sized community (hundreds of readers).
 you grow to many thousands, add a cached `days_completed` counter on `Reader`
 (updated in a `Checkoff` after_commit) and sort in SQL.
 
+## Troubleshooting
+
+**`ActiveRecord::DuplicateMigrationNameError: Multiple migrations have the name CreateBible270Readers`**
+
+You're on 0.6.2 or earlier, where the engine wrongly added its own `db/migrate` to the host app's
+migration paths *as well as* providing `install:migrations` — so copying them defined every
+migration class twice. Upgrade to >= 0.6.3 and keep your copied migrations:
+
+```bash
+bundle update bible270
+bin/rails db:migrate
+```
+
+**Sign-in returns 404 on the provider callback**
+
+OmniAuth's `path_prefix` doesn't match where the engine is mounted. They have to line up:
+mounting at `/reading-plan` means `path_prefix "/reading-plan/auth"`, and the URL registered with
+the provider must be `https://YOUR-HOST/reading-plan/auth/github/callback`. The install generator
+writes both consistently.
+
+**Clicking "Sign in with …" does nothing, or raises `OmniAuth::AuthenticityError`**
+
+The request has to be a POST with a CSRF token — OmniAuth 2.0+ refuses GET
+([CVE-2015-9284](https://nvd.nist.gov/vuln/detail/CVE-2015-9284)). The engine's own controls are
+already POST forms; if you've built your own link, convert it to `button_to`. Also confirm
+`omniauth-rails_csrf_protection` is in the bundle.
+
+**No sign-in email arrives**
+
+Email sign-in needs working Action Mailer delivery in the host app — the engine only calls
+`deliver_now` (or `deliver_later`). Check `config.mailer_from` is a real address your relay will
+accept, and watch the logs: delivery errors surface there. Nothing about a failure is shown to the
+reader, deliberately, since the "check your inbox" message is identical either way to avoid
+disclosing which addresses exist.
+
+**"That link has expired or was already used"**
+
+Links are single-use and live for `email_sign_in_ttl` (20 minutes by default). Some mail scanners
+and link-preview services fetch URLs before the recipient clicks, which consumes the token. If you
+see this a lot, lengthen the TTL or check whether something upstream is prefetching links.
+
+**Everything renders unstyled inside my layout**
+
+The engine ships scoped CSS in a partial rendered by its own layout. If you point
+`config.layout` at your application layout, add
+`<%= render "bible270/shared/styles" %>` to that layout's `<head>`, or style the `b270-*` classes
+yourself.
+
 ## Development / tests
 
 The deterministic plan logic is fully unit-tested with no Rails dependency:

data/lib/bible270/engine.rb

@@ -8,14 +8,14 @@ module Bible270
       g.orm :active_record
     end
 
-    # Make the engine's migrations available to the host via
+    # NOTE: we deliberately do NOT append the engine's db/migrate to the host
+    # app's migration paths. Rails already gives mountable engines the task
+    #
     #   bin/rails bible270:install:migrations
-    initializer "bible270.append_migrations" do |app|
-      unless app.root.to_s.match?(root.to_s)
-        config.paths["db/migrate"].expanded.each do |path|
-          app.config.paths["db/migrate"] << path
-        end
-      end
-    end
+    #
+    # which copies the migrations into the host's db/migrate, where the host
+    # owns them and they appear in schema.rb normally. Doing both would define
+    # each migration class twice and raise
+    # ActiveRecord::DuplicateMigrationNameError.
   end
 end

data/lib/bible270/version.rb

@@ -1,4 +1,4 @@
 # frozen_string_literal: true
 module Bible270
-  VERSION = "0.6.2"
+  VERSION = "0.6.3"
 end

metadata

@@ -1,13 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bible270
 version: !ruby/object:Gem::Version
-  version: 0.6.2
+  version: 0.6.3
 platform: ruby
 authors:
 - Andrew vonderLuft
+autorequire:
 bindir: bin
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2026-07-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -136,6 +137,7 @@ metadata:
   bug_tracker_uri: https://github.com/avonderluft/bible270/issues
   changelog_uri: https://github.com/avonderluft/bible270/blob/main/CHANGELOG.md
   rubygems_mfa_required: 'true'
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -150,7 +152,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.16
+rubygems_version: 3.4.19
+signing_key:
 specification_version: 4
 summary: 'A mountable Rails engine: a 270-day, verse-balanced Bible reading plan (OT
   once, NT twice, Psalms/Proverbs alongside) with per-user check-offs, comments, and