hello @erwinrooijakkers and @kelveden, thank you very much for your replies that helped me solve my issue. What I did is that : 1. I realized that in [duct/core “0.8.0”] a specific duct.profile/test was introduced (I was using 0.7.0), and upgraded to 0.8.0. This helped me avoid the creation of test lein profile 2. In my config.edn added a line (below the dev profile one) :
:duct.profile/test #duct/include "test.edn"
there is a small issue that caused me a crash in duct.core and this is why I had to introduce the “.edn” extension (https://github.com/duct-framework/core/issues/23)
and then : 3. added in duct_hierarchy.edn the code:
{:my-project.migration/h2 [:my-project.migration/sql]
:my-project.migration/postgres [:my-project.migration/sql]}
4. referenced :my-project.migration/sql in the config.edn file :
:duct.migrator/ragtime
{:migrations [#ig/ref :co.ytems.aeolus.migration/sql]}
5. defined the :my-project.migration/h2 in test.edn file and :my-project.migration/postgres in both dev.edn and prod profilesthanks again for your help ! 👍
1🙂Hopefully this one's an easy one for anyone using Ataraxy - the templated response looks like:
[::response/ok {:example "data"}]
Could someone tell me if it's possible to use this vector response format while also adding new HTTP headers, or should I move on to a normal Ring response?