- all catalog services (update/software/highlighted/builds/file/file-manager/ download/image + SoftwareResponseBuilder), the SoftwareUpdater platform services and their concerns, Blueprinter serializers (incl. TimestampFields) and the 4 DTOs now live in the engine under WarpEngine:: - constantize dispatch strings use absolute names (WarpEngine::SoftwareUpdater::<Platform>Service) - container paths read from WarpEngine.config everywhere (FileService, DownloadService, FileManagerService, ArchiveExtraction, ReleaseSerializer path rewriting); FileManagerService base path is now lazy - engine requires blueprinter itself; gemspec declares blueprinter + rubyzip - engine test suite: spec/dummy app (mysql warp_engine_test, catalog-only schema), rails_helper with engine-local factories; catalog model/service specs and factories moved from the host - host suite keeps TTG specs and loads catalog factories from the engine Verified: engine suite 40 green, host suite 14 green, /api/software and /api/builds byte-identical to baselines, admin OK. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
9 lines
258 B
YAML
9 lines
258 B
YAML
test:
|
|
adapter: mysql2
|
|
encoding: utf8mb4
|
|
username: <%= ENV.fetch("DB_USER", "root") %>
|
|
password: <%= ENV.fetch("DB_PASSWORD", "") %>
|
|
host: <%= ENV.fetch("DB_HOST", "mysql") %>
|
|
port: <%= ENV.fetch("DB_PORT", "3306") %>
|
|
database: warp_engine_test
|