Different index based on where project was built

[eemi]

Hey guys! I'm using gitlab to host my project and their's CI feature to build the site.

I'm running Middleman with ruby:2.4.1 and node 8.4. I use this setup in both my machine and the gitlab ci runner.

The search.json file built by each machine is different. In my machine in both environment (development and build env) the index is the same. Im running a simple handmade sitemap.xml by going trough Middleman's sitemap and is the same in both machines (although the order the items is different).

There's any way to see a log of what's getting into the index? Maybe that could help me to understand whats wrong.

regards

[matiasgarciaisaia]

Hi @eemi!

Here's where the extension indexes resources. You can probably drop some puts and/or binding.pry there and check which resources are being indexed. Watch out there are a couple of conditions to skip a resource, also.

If you find a nice way to add some (optional) logging to the extension, that'd be a nice PR :)

Hope this helps!

[eemi]

@matiasgarciaisaia I'm still trying to understand what's wrong with my setup. For the moment, using https://github.com/sn3p/middleman-search/tree/update-lunr fixes the problem.

Thanks as usual, I will update this as soon as I have more info.