Both are valid options. Personally I prefer passing dependencies down explicitly because then it’s very clear where the deps are coming from. I usually have a function that receives the dependencies from integrant and returns a reitit router. Here’s one example: https://github.com/lipas-liikuntapaikat/lipas/blob/master/webapp/src/clj/lipas/backend/handler.clj#L51 https://github.com/lipas-liikuntapaikat/lipas/blob/master/webapp/src/clj/lipas/backend/system.clj#L27

That looks great, thanks for the help!

As an alternative, and as alluded to at the start, I perfer to stick my dependencies in an app-config that is injected into the requst via middleware:

https://github.com/dharrigan/startrek/blob/master/src/startrek/shared/middleware/app_config.clj

I then pull out the app-config from the request and anything within the map

Both are ways of doing the same thing 😉

This is roughly how I had it before but I injected the clients separately, but al in one map is a good idea as well. Thanks!

Yes you can! I have done the exact same thing.

I put the reitit routes early in the ring middleware chain and check if they return a response. If not, I pass the request on to the next handler.

mmmm I’ll try that tmr, can I reach out to you?

Can you share a snippet?

Very schematically it looks like this (haven't confirmed this actually works but I think it should)

(def routes
  ["reitit/routes/here"])

(def reitit-handler
  (reitit-ring/ring-handler
   (reitit-ring/router
    routes)))

(defn reitit-middleware
  [handler]
  (fn [request]
    (or (reitit-handler request)
        (handler request))))

(def app
  (-> your-compojure-routes-middleware
      reitit-middleware
      ;; other middleware
      ))

Also check out reloading-ring-handler in the latest release of reitit.

Thanks, I’m going to take a look!