This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author epicfaace
Recipients Mariatta, brett.cannon, docs@python, epicfaace, willingc
Date 2020-03-15.23:06:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584313603.53.0.106958957633.issue37860@roundup.psfhosted.org>
In-reply-to
Content
GitHub Pages has no limit on "build limits" like Netlify does.

One limitation of this approach, though, is that GitHub Pages sites are limited to 1 GB in size. Each doc build is 50 MB, meaning that we could host at a maximum 20 builds. If we needed to, we could resolve this by doing one (or multiple) of the following:
- check with GitHub to see if they will increase the limit for this case
- only build PRs that have been tagged "documentation"
- add a workflow to automatically remove deploy previews after a certain amount of time has passed or after a PR has been merged
- don't deploy on GitHub Pages, but use something like https://surge.sh/, which apparently doesn't have a hard limit on size of a static site
History
Date User Action Args
2020-03-15 23:06:43epicfaacesetrecipients: + epicfaace, brett.cannon, docs@python, willingc, Mariatta
2020-03-15 23:06:43epicfaacesetmessageid: <1584313603.53.0.106958957633.issue37860@roundup.psfhosted.org>
2020-03-15 23:06:43epicfaacelinkissue37860 messages
2020-03-15 23:06:43epicfaacecreate