Content-Length: 215434 | pFad | http://github.com/manastech/middleman-search/issues/33

80 Different index based on where project was built · Issue #33 · manastech/middleman-search · GitHub
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Different index based on where project was built #33

Open
eemi opened this issue Sep 7, 2017 · 2 comments
Open

Different index based on where project was built #33

eemi opened this issue Sep 7, 2017 · 2 comments

Comments

@eemi
Copy link

eemi commented Sep 7, 2017

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
Copy link
Member

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
Copy link
Author

eemi commented Sep 9, 2017 •
edited
Loading

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eemi @matiasgarciaisaia








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/manastech/middleman-search/issues/33

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy