Brian Porter

There wouldn't happen to be a guide or wiki article written about "how to write gollum plugins", would there? I recognize the general idea is to intercept Rack http requests...

Is it bad form to squat in the `Gollum::` namespace? I started a gem (named `gollum-elasticsearch`) and `bundle gem` defaulted to `Gollum::Elasticsearch`. I suspect probably it is **not** wise to...

Thanks, as always, for the thoughtful responses. I have a couple quick updates from the weekend: - I went with `Gollum::Elasticsearch` for now. If it needs to change, I'll change...

Oh and the work-in-progress is here: https://github.com/beporter/gollum-elasticsearch

> I don't know if there is any documentation around this but I'd be interested in helping to create some if there isn't any. It's also quite possible that my...

I have no particular allegiance to Elasticsearch, it's just what I happened to be familiar with. 🤷 From looking at the others, the APIs seem similar so this could end...

Also to loop back to @benjaminwil's discussion about creating extension points... That's usually done via two mechanisms: Lifecycle hooks (also known as "callbacks"), or an event bus. Rails (and ActiveRecord...

Also interested in regaining this awesome feature. Anything we can do to facilitate progress? Does #83 need to be rebased?

This was a killer feature for CakePHP 2's [Migrations plugin](https://github.com/CakeDC/migrations/blob/master/Docs/Documentation/Migrations.md#auto-migration-files). (Alas, abandoned since Cake 3 switched to Phinx.) I found that the safest and quickest way to build a migration...

That's totally fine. For reference, I started a repo for this work as a plugin here: https://github.com/beporter/gollum_search But it's on the back burner currently. As things are often wont to...