-
Notifications
You must be signed in to change notification settings - Fork 128
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
[DOC] Local documentation build #1896
Comments
@aadya940 relevant to our discussion today |
Run the following command from project root Directory.
Then run the other steps of make. |
I remember trying out the sphinx command yesterday but I didn't start a http server as you describe. Could you explain this step again, I don't really get what you mean? |
Just tried to run this before
I don't think that is really required, as the static HTML can be directly opened in webbrowser. |
You'll have to delete the old files generated by the |
|
@IRKnyazev @Cyril-Meyer For me, this #1905 works, you can try following the steps and let me know if you have issues. :)) |
@aadya940 |
I still can't see my docstring changes locally :( Originally I would run |
@IRKnyazev
|
@IRKnyazev Yes, so the thing is , running only After deleting these files, you'll have to run the Hope you get the point :)) |
I'll try to have a go at this today and see if I can get it to work 🙂 |
Hi everyone, this all worked fine for me only using
Examples are missing due to the messed up symlink, but everything else seems fine. Refreshing for docstring changes:
It is definitely generating the relevant files and updating them on my end. No manually deleting files or running sphinx-apidoc. |
Did you run |
@IRKnyazev @Cyril-Meyer @aadya940 If you find some time to test the above (replace batch file with makefile if possible) that would be helpful. Mention if you installed with |
I'm not sure, but knowing myself, I copied and pasted lines from the documentation, so, my setup is probably the following :
(Win10 Python 3.10.11)
I just tested again right now, with cmd and git bash (but neither use the makefile).
I do all my test on the branch I identified the problem (#1892), so I can check if the arsenal ref is changed with the new one. After all of this, I checked things manually. My python file is good with new docstring.
Again, I don't understand why this, you can just open the index.html file in any browser. |
yeah
I again had no issue running step 3 to update the autogenerated api file and it changed after refreshing. Could you maybe take a look as someone not trapped on Windows @chrisholder 🙂. |
#2297 updates the documentation for the above among other things. Hopefully Chris can give it a troubleshoot for other OS. |
I can recreate this on both linux (Ubuntu 22.04) and macos (Sequoia 15.0.1). Same issue - when I update the docstrings the documentation website does not update. The only way to make it update is to rebuild the entire docs. |
Could you expand on what you mean by rebuild the entire docs? Weird that |
I mean re-running the following:
If I change anything in the docs, to update it on the local website I have to stop the server and rerun the above commands. |
That is expected, do you need to run the server though or can you just open the html doc in a browser and update it using make? |
Spoke to matt for clarity and the docs on linux and macos are working fine for me. I initially thought the conversation was about hot reloading the website as soon as you make a change. On both linux and macos when I make a change to the docs and rerun |
Describe the issue linked to the documentation
In documentation-build it is stated that :
It works, but "if it is docstring changes, you have to make sure all the API pages are being regenerated." (@MatthewMiddlehurst on slack in #help-desk)
As much as I know, I'm not the only one struggling with local build of documentation (e.g. to check if it works before PR), @IRKnyazev opened the discussion on slack and most of the current answer are "PR then check result".
Suggest a potential alternative/fix
There is a problem with those instructions, we need to correct them.
The text was updated successfully, but these errors were encountered: