Skip to content
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

Keep duplicate of root-ref in its own directory (future proof). #15

Closed
Robpol86 opened this issue Aug 8, 2016 · 0 comments
Closed

Keep duplicate of root-ref in its own directory (future proof). #15

Robpol86 opened this issue Aug 8, 2016 · 0 comments

Comments

@Robpol86
Copy link
Collaborator

Robpol86 commented Aug 8, 2016

  1. Sometimes people edit URLs to go to the latest version (e.g. they're on v1.0.1 and they know v2.0.0 is the latest so they go there directly). If v2.0.0 is the latest they'll get a 404 since it's the root ref. Once v2.0.1 is out then /v2.0.0/index.html works.
  2. When the developer switches root ref to master until the next release, /v2.0.0/index.html will exist. Then they switch back the root ref to greatest tag and now /v2.0.0/index.html doesn't work until they make the release.

Solution: when building, build the root ref twice. Once in the root and again in /.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant