:extra-paths in ions deployment

My codebase has directories env/dev and env/prod, under which are defined alternative versions of the same namespace my-app.env. The directories are not included in the regular :paths in deps.edn, but are added as :extra-paths under aliases for :dev and :prod.

When deploying using ions, my-app.env is not found, and the deploy fails.

Is there a way to configure things so that the options under the :prod alias are active in the deployed version? For now I’ve just added the prod dir to the top-level :paths, and the deploy succeeds.

If there’s a more idiomatic way to achieve the same thing, that would be even better.

Thanks in advance.

1 Like