I added a new example for using CircleCI v2 with Boot, works a lot better now, no more problems with caching and inotify watches: https://github.com/boot-clj/boot/wiki/Running-Boot-on-CI-systems#circleci-v2

anybody has a tip on how to debug what is going on here? https://github.com/boot-clj/boot/issues/607

my clojure/java foo is not strong enough

more concretely: how to debug why the watcher from https://github.com/boot-clj/boot/blob/master/boot/core/src/boot/core.clj#L729 stops calling the callback fn

folks have to constantly restart the boot instance to get it working again, which isn’t…. ideal

can this be related to https://github.com/boot-clj/boot/issues/477?

@kommen, I wonder if this is some problem with inotify and Docker… I assume you're watching some mounted host directory with boot?

Which host os are you using, by the way?

@miikka we’re using this as the base image: https://hub.docker.com/_/node/

and no, it doesn’t seem to be an issue with inotify and docker. a another boot process running in same container is still getting and processing the events

does boot offer a way to modify dependencies and auto-require them for different builds?

Initially I wanted something like this: dynamically require certain dependencies depending on a clojure-defines compiler flag e.g.

(ns my.ns (:require
[my.dependency :as a]
(when goog.DEBUG [clojure.test.check]))

Looks like I might be able to get away with something using :preloads https://github.com/clojure/clojurescript/wiki/Compiler-Options#preloads

you can use a different namespace as entry point and require you.project.core from there

What would a :not-found handler in boot-http look like to support pushState? It seems like you'd want to just serve the same index HTML file that is set by default but :not-found expects a ring handler, not Ring middleware. Am I missing something here? /cc @pandeiro

Relevant line: https://github.com/pandeiro/boot-http/blob/master/src/pandeiro/boot_http.clj#L53

@kenny Yeah, I think as originally contributed, it takes a symbol pointing to a handler function. But it could also just take a string representing a file or resource and serve that. PR welcome.

Will take a look now.

@pandeiro Would you be opposed to me adding a new option called not-found-middleware?

Actually it's not really middleware. It'd essentially be a replacement for not-found-handler.

You can open an issue and we can discuss, but IMO the nicest API would be to reuse the same option for both different ways of handling: function and static file

@pandeiro Oh I can totally use the same option for both. However, that would introduce a breaking change and I was trying to avoid that.