-
Notifications
You must be signed in to change notification settings - Fork 0
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
Html pages don't work #24
Comments
Oh, I'm sorry I should have mentioned it. It's not because of the transition to https instead of http, but sadly because I had to make space on the server. These html files were generated not with Unlike with The result is that the directory took up 12Gb of space on the server, and there was simply no space left for compiling and running The simplest way to fix this would be to have the "structured version" links link to the new version (just adding |
Now that the old STS pages have been replaced, and considering that metamath/metamath-exe#9 will probably not be merged, what's your direction for the future? These are the scenarios that came up in my mind:
|
I think the layouts of both metamath-web and the STS pages are aesthetically pleasing, so I personally don't have strong opinions on that. |
Thanks to metamath/set.mm#3611, I could update the pages to the latest version of set.mm. |
Nice! I think once it's confirmed that it's working properly, this issue can be closed. |
It looks good on my end, the script was run every day and the latest There is a downtime of a few seconds for parsing the database, so I think I could even update a few times a day without this downtime being much noticeable. |
Once a day or a few times a day are both fine for me, feel free to do what you think it's best. |
This problem seems to hold for all theorems in the database, below I show an example with
bezout
.From https://us.metamath.org/mpeuni/bezout.html
I click
structured version
on the top right.This links to http://metamath.tirix.org/bezout.html
Which shows a 404. Some days ago it worked fine, since I showed it as example in the mailing list. So maybe now it doesn't work because of the transition to https instead of http?
The text was updated successfully, but these errors were encountered: