- update, files and the 6 /api catalog controllers now live in the engine on a new WarpEngine::ApiController base (same rescue/mime behavior as host) - engine routes serve /update, /file/*path, /api/software*, /api/builds*, /api/image/:id, /api/download at unchanged public paths via the root mount; host routes keep only TTG endpoints (events, members, wiki, rss, swagger) - /update secret comes from WarpEngine.config.update_secret and an unconfigured secret now rejects every request (previously an empty UPDATE_SECRET env accepted empty secrets) - apipie-rails is an engine dependency (DSL in engine controllers); dummy app configures apipie with validation off, mirroring the host - engine request specs: catalog controller specs moved from host plus new /update auth contract spec Verified: engine suite 53 green, host suite 6 green, /api/software and /api/builds byte-identical to baselines, /update 401/400 behavior intact, admin and TTG endpoints OK. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
12 lines
319 B
Ruby
12 lines
319 B
Ruby
Apipie.configure do |config|
|
|
config.app_name = "WarpEngine Dummy"
|
|
config.api_base_url = ""
|
|
config.doc_base_url = "/api/docs"
|
|
config.api_controllers_matcher = [
|
|
"#{WarpEngine::Engine.root}/app/controllers/**/*.rb"
|
|
]
|
|
config.validate = false
|
|
config.translate = false
|
|
config.default_version = "1.0"
|
|
end
|