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

An easy way to configure redirects #51

Open
thanethomson opened this issue Feb 28, 2023 · 0 comments
Open

An easy way to configure redirects #51

thanethomson opened this issue Feb 28, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@thanethomson
Copy link
Contributor

I suspect that, at some point soon, we're going to need some kind of simple mechanism to specify redirects.

For instance, we're currently making our v0.37.0 release candidates' docs available via https://docs.cometbft.com/v0.37-rc/, but soon, when we cut v0.37.0, the documentation will be available from the /v0.37/ path and not from the /v0.37-rc/ path any more.

With the old Vuepress-based site, there was a simple REDIRECTS file (similar to the VERSIONS file in this repo) that allowed us to specify:

/old/path/ /new/path/
/old/path/2/ /new/path/2/

Where this would automatically generate index.html files at /old/path/index.html that would redirect to /new/path/.

It'd be great if we could implement the same or a similar mechanism that achieves the same kind of outcome in an easy way. The question of where to store it, however, is still up for debate (i.e. for this particular file, do we store it in the cometbft repo, or in the cometbft-docs repo?).

@thanethomson thanethomson added the enhancement New feature or request label Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Todo
Development

No branches or pull requests

1 participant