Separate database.yml for wasm

Author: rossta

.github/workflows/verify.yml

@@ -256,6 +256,7 @@ jobs:
           path: public
       - run: ls -lahR public
       - run: echo ${{ secrets.RAILS_MASTER_WASM_KEY }} > config/credentials/wasm.key
+      - run: cp config/database.wasm.yml config/database.yml
       - run: mkdir -p .wasm
       - name: Build rails wasm for web
         run: TARGET=${{ matrix.target }} bin/wasm/build

config/database.wasm.yml

@@ -0,0 +1,75 @@
+# SQLite. Versions 3.8.0 and up are supported.
+#   gem install sqlite3
+#
+#   Ensure the SQLite 3 gem is defined in your Gemfile
+#   gem "sqlite3"
+#
+default: &default
+  adapter: sqlite3
+  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 3 } %>
+  timeout: 5000
+  extensions:
+    - sqlite_ulid
+
+development:
+  primary:
+    <<: *default
+    database: storage/development/data.sqlite3
+  cache:
+    <<: *default
+    database: storage/development/cache.sqlite3
+    migrations_paths: db/migrate_cache
+  queue:
+    <<: *default
+    database: storage/development/queue.sqlite3
+    migrations_paths: db/migrate_queue
+  cable:
+    <<: *default
+    database: storage/development/cable.sqlite3
+    migrations_paths: db/migrate_cable
+
+# Warning: The database defined as "test" will be erased and
+# re-generated from your development database when you run "rake".
+# Do not set this db to the same as development or production.
+test:
+  primary:
+    <<: *default
+    database: storage/test/data.sqlite3
+  cache:
+    <<: *default
+    database: storage/test/cache.sqlite3
+    migrations_paths: db/migrate_cache
+  queue:
+    <<: *default
+    database: storage/test/queue.sqlite3
+    migrations_paths: db/migrate_queue
+  cable:
+    <<: *default
+    database: storage/test/cable.sqlite3
+    migrations_paths: db/migrate_cable
+
+# SQLite3 write its data on the local filesystem, as such it requires
+# persistent disks. If you are deploying to a managed service, you should
+# make sure it provides disk persistence, as many don't.
+#
+# Similarly, if you deploy your application as a Docker container, you must
+# ensure the database is located in a persisted volume.
+production:
+  primary:
+    <<: *default
+    database: storage/production/data.sqlite3
+  cache:
+    <<: *default
+    database: storage/production/cache.sqlite3
+    migrations_paths: db/migrate_cache
+  queue:
+    <<: *default
+    database: storage/production/queue.sqlite3
+    migrations_paths: db/migrate_queue
+  cable:
+    <<: *default
+    database: storage/production/cable.sqlite3
+    migrations_paths: db/migrate_cable
+
+wasm:
+  adapter: nulldb

config/database.yml

@@ -72,6 +72,3 @@ production:
     <<: *default
     database: storage/production/cable.sqlite3
     migrations_paths: db/migrate_cable
-
-wasm:
-  adapter: nulldb