Ben Smith

Done in #514.

You **must not** use the `concurrency` option with an Ecto projector as it expects events to be processed sequentially and in order. If the `concurrency` option is specified for an...

@KevinColemanInc This appears to be fixed by commit 4f862f7d1f5bdd1aab3d7fdb602f022a3c138d63 but has not been published to hex. A workaround is to reference that commit hash in `mix.exs`: ```elixir defp deps do...

Happy to accept a pull request to bring the code up-to-date.

@paxperscientiam Workaround for you is to use [nvm](https://github.com/creationix/nvm) to install and use an earlier version of Node. ``` nvm install v4.1.0 nvm use v4.1.0 ```

For reference you can write a function to reset an event store as follows: ```elixir alias EventStore.Storage.Initializer def reset_storage! do config = MyEventStore.config() with {:ok, conn}

> I did end up writing my own function that does so at the query level and gives me what I need. it COULD (and should) be a part of...

The two changes we want to make are to modify the default aggregate lifespan behaviour defined by Commanded to not keep aggregate processes running indefinitely and to allow this default...

This looks like it could be a pain for someone (likely me!) to maintain going forwards. I'd rather not have to support a Dockerfile and docker-compose just for development, unless...

Having three similarly named functions is too confusing (`init/0`, `init/1` and `initialize/1`). The `init/1` function is called _before_ the event handler process is started to optionally configure the handler with...