-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Fix search bar on documentation website #3423
Comments
Longer version of the steps for fixing this: https://blogs.msdn.microsoft.com/africaapps/2013/06/07/how-to-serve-static-json-files-from-a-windows-azure-website/ |
Trying this out on another project where we use a similar DocFx setup to Akka.NET |
Also going to need to enable a specific DocFx step in order to get this working: dotnet/docfx#2679 (comment) |
(that step produces the index.json) |
@Aaronontheweb I can have a look at this. Where are the search bar & the index.json located in code? |
I've forked & cloned the docs site repo. However I've run into this:
Can anyone advise how to get past that? Unfortunately grunt is not my speciality (I'm more of a gulp/webpack person). |
Also, I seem to be unable to locate the docfx.json to add the |
The old documentation repo located at (https://github.com/akkadotnet/getakka.net) has been abandoned and is only there for legacy / information purposes. So we ported everything over to using DocFx and is now located in our main repo (https://github.com/akkadotnet/akka.net/tree/dev/docs). @akkadotnet/core We should probably put a huge disclaimer on the old repo and point them to the docfx stuff. |
@sean-gilliam can you tell me how do I run the site locally to test the fix? Is this a static site served from IIS? |
If you clone the main repo, just need to run |
We've known that the search functionality on the site has been busted for a while, but I received an email from an end-user that explains how to fix it (they also use DocFx):
Since we're using Azure Websites to host the docs, which IIRC is running on IIS, we should be able to slap that configuration at the root of the website and fix it that way.
The text was updated successfully, but these errors were encountered: