Closed bennibbelink closed 1 week ago
FROM cyclus_20.04_apt/cyclus:latest
FROM cyclus_20.04_apt/cyclus:stable
FROM cyclus_20.04_conda/cyclus:latest
FROM cyclus_20.04_conda/cyclus:stable
FROM cyclus_22.04_apt/cyclus:latest
FROM cyclus_22.04_apt/cyclus:stable
FROM cyclus_22.04_conda/cyclus:latest
FROM cyclus_22.04_conda/cyclus:stable
I'm happy to merge this now and wait for style sheet cross-repo fixes...
Something odd is happening... the new style changes (for cyclus) are present in the artifact generated by cyclus.github.com actions but I'm not seeing them in the published site. The docs were present before adding them back into the build so I'm wondering if there's another server somewhere?
Aha! The cyclus repo has Pages set up to serve the docs. Is it okay if I turn this (and the cycamore one) off? That way the docs will be accessible from just the cyclus.github.com site
Just to make sure I understand... it seems that https://fuelcycle.org/cyclus/api/
is resolving to be the pages
that are produced by GitHub at cyclus/cyclus
on the gh-pages
branch?
And that is blocking the ability to simply serve docs from the website file structure....
I think it's probably OK to turn of pages since the same URL will serve the new information and we never had a mechanism to automate the update of the go-pages
.
The other alternative would be something that guarantees that the gh-pages
are updated with every merged PR and/or release.
it seems that https://fuelcycle.org/cyclus/api/ is resolving to be the pages that are produced by GitHub at cyclus/cyclus on the gh-pages branch?
And that is blocking the ability to simply serve docs from the website file structure....
Yes, this is my understanding.
The other alternative would be something that guarantees that the gh-pages are updated with every merged PR and/or release.
That is also an option. It would require that we maintain actions in cylus and cycamore to do this. I think I would lean toward managing all of the site content in one place (cyclus.github.com's Dockerfile) for the sake of transparency. Having subpaths of a website served from separate repositories doesn't feel very intuitive, and is part of the reason it took me so long to understand where those docs were being produced.
Also I went ahead and changed this to find the stylesheet/gif at the location installed by cyclus.
Makes essentially the same changes as https://github.com/cyclus/cyclus/pull/1787
zip for preview html.zip