Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up404 in archives/ during new releases #68
Comments
|
For the record, it happened again on the 3.7.2 release. I fixed it manually again using the previous commands (just changed the versions). |
|
Another way to do it is to start manually a build_docs right after a release: |
|
Not sure how it all work.. can we not display the new download URLs before the downloadables have finished getting built? |
|
@Mariatta that's an idea. The issue is we're building HTML multiple time a day, but PDF only once a day, so it happen that some release get their HTML build before their PDF. |
|
What is needed to ensure that both PDF and HTML get built at release time, instead of waiting for the cron to run? |
|
There's #77 that should have the side effect to solve it, by running the build only when needed it could rebuild everything. But it's a lot of work and I did not found the free time to do it. A simple solution in the meantime would be to stop the cron building HTML only, keeping only daily full builds (html + pdf), I don't think we need the HTML doc to be updated every 3 hours, what do you think? |
|
I think building them once a day sounds good and could reduce the number of 404 reports we're getting. And we are certain that by the time the HTML is done building. and rendered, the PDFs are also finished? |
On the release of 3.7.2rc1, the archives/ were not built automatically (they are built daily).
I bet (didn't checked it yet) that it should fix itself in less than 24h, while the cron passes, but it's too long and it bothers people.
I had to build locally then from the local
www/directory run:Then remotely run:
to temporary trash-fix this.