You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
createRedirects(existingPath){// For every /docs/X path, also create /documentation/Xif(existingPath.startsWith('/docs/')){returnexistingPath.replace('/docs/','/documentation/');}returnundefined;}
module.exports={plugins: [['@docusaurus/plugin-client-redirects',{createRedirects(existingPath){// Redirect old /documentation/ URLs to new /docs/ URLsif(existingPath.includes('/docs/')){// Create redirects from /documentation/{version}/{page} to /docs/{version}/{page}return[existingPath.replace('/docs/','/documentation/'),];}returnundefined;},// Or explicit redirects for specific pagesredirects: [{to: '/docs/1.28/',from: ['/documentation/current/','/documentation/1.28/'],},// Add more as needed...],},],],};
Besides several google search results resulting in 404s, it has also broken links across docs within cloudnative-pg docs.
For example:
docs/1.28/backup has a recommendation to use the Barman Cloud Plugin Via [CNPG-I](https://github.com/cloudnative-pg/cnpg-i/) plugins: the CloudNativePG Community officially supports the [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/) for integration with object storage services.
The above has several broken links on just the intro page, but they are throughout the entire repo. This is especially frustrating when there are instructions at https://cloudnative-pg.io/docs/1.28/backup recommending the plugin over the native implementation, but the recommended approach is filled with dead links.
I assume rolling this back would cause more problems but wondering why it was done in the first place. In any case, really needs redirects in place until all docs are updated.
Activity
jmealo commentedon Dec 23, 2025
Unless we put Cloudflare in front of Github Pages, it looks like we'd need to do client-side redirects:
https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-client-redirects
It says these are always inactive in development, and only active in production, so during testing, make sure you're on a production build.
jlroskens commentedon Jan 6, 2026
Besides several google search results resulting in 404s, it has also broken links across docs within cloudnative-pg docs.
For example:
Via [CNPG-I](https://github.com/cloudnative-pg/cnpg-i/) plugins: the CloudNativePG Community officially supports the [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/) for integration with object storage services.The above has several broken links on just the intro page, but they are throughout the entire repo. This is especially frustrating when there are instructions at https://cloudnative-pg.io/docs/1.28/backup recommending the plugin over the native implementation, but the recommended approach is filled with dead links.
I assume rolling this back would cause more problems but wondering why it was done in the first place. In any case, really needs redirects in place until all docs are updated.
jmealo commentedon Jan 6, 2026
I think putting Cloudflare in front and doing rewrites is probably the best option.
gbartolini commentedon Jan 15, 2026
I have asked the CNCF if it is possible to get some help here.
gbartolini commentedon Jan 18, 2026
I have put a temporary patch with @sxd, through client-side HTTP redirects. This is related to #24.
Check cloudnative-pg/cloudnative-pg.github.io#404
feat: add version 1.26 (unmaintained) (#30)
feat: add version 1.25 (unmaintained)
feat: add version 1.25 (unmaintained)
feat: add version 1.25 (unmaintained) (#35)