I have a frontend service that serves a simple SPA, and reverse proxies requests to the /api route to the backend using Caddy. Thus, my deploy script is "caddy run --config Caddyfile".

This is all fine and dandy until i migrated to RAILPACK from NIXPACKS.

NIXPACKS seemed to automagically detect caddy as a dependency for me and deployed with no issue. However, when using RAILPACK, it fails to detect the need for caddy, and the build crashes during the deploy phase since caddy is not installed.

I have since migrated back to NIXPACKS to just get the app running again, but I do wish to stay up to date with Railway's development.

I was just wondering if there was a more explicit way to define dependencies with RAILPACK using the standard Config as Code feature.