stan-dev / stan-dev/docs

Docs repo is too big to deploy

Open
#928 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TeX
Stars
43
Forks
133
Avg merge
11h 32m
Merged PRs (30d)
4

Description

The GitHub Pages limits page states that you will not be able to serve a github pages repository that is larger than 1GB, which as of this morning our deployment here now is. This is blocking the docs being published for the new 2.38 release (https://github.com/stan-dev/cmdstan/issues/1333)

Most of the size is from the old, pre-quarto docs. Here's the breakdown:

1.2G    .
82M     2_33
81M     2_32
80M     2_31
79M     2_30
74M     2_29
68M     2_28
65M     2_27
63M     2_26
63M     2_25
62M     2_24
57M     2_23
46M     2_22
46M     2_21
46M     2_20
45M     2_19
44M     2_18
24M     2_38
24M     2_37
23M     2_36
23M     2_35
22M     2_34
6.7M    stan-users-guide
4.1M    functions-reference
3.7M    search.json
2.5M    reference-manual
1.7M    site_libs
1.5M    cmdstan-guide
644K    sdlc.html
392K    img
52K     index.html
32K     404.html
12K     theming
12K     quarto-config
8.0K    quarto_styles.css
4.0K    google9e4c7002947f3d44.html

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by measuring the repository and reviewing the old pre-quarto directories listed in the size breakdown, along with the GitHub Pages deployment configuration. Identify what can be removed or excluded without affecting the current documentation; done means the repository is below GitHub's 1 GB limit and the 2.38 docs can be published.

Written by the indexing model from the issue text.

Assessment

Tech stack
tex
Domain
devops, documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.