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
Updating doc building to Sphinx 4.3.2 (python 3) #2662
Conversation
Awesome stuff @barsch. I like the overall looks, and I'm real happy that we'll have a proper navigation again (with the left side bar). Can you put the exact version numbers of the build environment somewhere, I can help set up the cron jobs later.. or.. we could have @d-chambers and @heavelock give a shot at building docs in gh-actions? Might be the right time to give it a try, since we would have to set up docs building on new server from scratch more or less anyway? Also, can you put the build log as a gist maybe.. interesting to see if it got any more readable at all compared to the 80-page warning/error logs we used to have |
@megies its already build on the new server (manually atm) - log can be found here https://docs.obspy.org/sphinx3/log.txt |
OK, oof, still such a bookshelf of warnings. |
jupp - and still takes ages to run - its not fun working on it ... |
No kidding, it might easily be the most painful thing to work on in the whole project. |
Hey I was browsing the docs and saw that there are some bits where sphinx links to the builtin It's a very small thing and it seems like you've got enough work cut out already, but I thought I'd point it out since you're updating the docs. It might be solved using the https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-samp |
Hey! I had some spare time today and I thought about finally working on building docs on GithubActions. Coming from GitlabCI this action systems seems to be weird but I think I managed to make the builder run. Check it out on PR against my fork: It's based on obspy/sphinx3 branch that was rebased on top of current master From some of the important changes in the code of docs itself I changed m2r dependency to m2r2 that is a fork of the former one which is not maintained anymore. |
Oh dammit. I accidentally pushed to wrong remote and my changes got in here. Sorry for that as I meant to first ask before doing that ... Anyway, should I remove my changes or can they stay here? My changes include:
|
All fine - knock yourself out ;) |
Since we are at the docs, do you think it would beneficial for us to start using some linter for docs? What do you think? |
Basemap -> Cartopy conversion progress:
|
@heavelock first of all big thanks for looking into this! Two rants from my side while you are on it:
|
And the second point: |
docker would be perfect imho |
perf. I had it already done but then I ditched it because the sphinx-action I am using here does not support using a custom image as argument. I could fork it and have our own action for that or just create a custom workflow. Positive side of the action is that it is parsing the warnings from sphinx and dropping them in diff. |
I testes the Edit: Bugfix for that will be included in 4.0.0: |
@barsch Would you mind forking this repo as organization? https://github.com/ammaraskar/sphinx-action |
|
my turn to give it a go :-) |
2022 changes
Example output: http://msnoise.org/obspy-doc/ on my local machine, the first build took also ~20 minutes, successive builds (adding one comma to one RST file): less than 2 minutes. This means, running a doc builder that doesn't redo everything from scratch could produce docs in a flash. That'd require having some workflow which would include some "persistence": first run ever (ever)
successive builds:
TODO still:
|
I reverted my changes here and created a new branch at PR #2947. |
What fits best for you. I skimmed through changes introduced by this PR and I didn't find any obvious glitches. Maybe we can try to get rid of the image replacements of |
I wouldn't try to automate this via GH actions if not needed as this has failed in the past after updating dependencies etc. Instead I suggest we just leave the the |
I checked ObsPy's sectret tab and:
Because we want to see doc builds also from forks, it will not work to deploy the doc via SSH in a run triggered in the doc building workflow. We either need a separate github action checking in a time interval for artifacts to upload. Or straightforward, the server can check for runs and relevant artifacts on its own. So the doc building would still be on github actions and can be maintained in this repository, but the server fetches and deploys the docs. |
I very much prefer that. |
Great. @barsch Do you want to write the necessary server-side code? I could also do it. This PR can serve as test load. |
there should be code which could be recycled here: https://github.com/obspy/obspy/tree/master/misc/scripts/docs_buildbot
I'm happy to maintain/admin the server and obspy-reporter, but as stated before coding for obspy is not really on my agenda any more - didn't use obspy since 10 years or so and its about time other take over ;) (but I'm actually very impressed and quite happy to see huge progress here) |
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS http://msnoise.org/obspy-doc/packages/autogen/obspy.core.event.Event.plot.html#obspy.core.event.Event.plot |
hmm https://docs.obspy.org/sphinx3/gallery.html vs. http://msnoise.org/obspy-doc/gallery.html for whatever reason custom.min.css is not used |
ah, indeed, that... checking now- difference is that on your site div has class "gallery" and not on mine |
CI was 🟢 , which is very satisfactory :-) And move on with, on the DOC side: the doc builder and on the code side: remove all basemap stuff |
249 commits +2,927 −3,259 ... wow I will squash to "1 commit" to merge in master :-) |
This PR updates the docs build process to Sphinx 3.1.1. After unsucessfully trying to fix the old doc builder I decided to restart the whole process from scratch and reimplement existing features afterwards.
A preview of the current results can be seen here: https://docs.obspy.org/sphinx3/
Feel free to participate - running the doc building takes unfortunatly ages ... If someone could rewrite all examples using basemap to cartopy would be a big help.