Consuming pgbackrest documentation

[pipetogrep]

Sources

https://github.com/EnterpriseDB/pgbackrest-build-and-tests

the branch is here:
https://github.com/EnterpriseDB/pgbackrest-build-and-tests/blob/docs_development/

the folder with all the md files is here:
https://github.com/EnterpriseDB/pgbackrest-build-and-tests/blob/docs_development/docs

The initial file currently is this file:
https://github.com/EnterpriseDB/pgbackrest-build-and-tests/blob/docs_development/docs/README.md

Implementation

• Can we use the docs_development branch for the PoC?

[epbarger]

Merged in the proof of concept for this. Using hardcoded files for now until we have a service user account I can pull from (or the repo becomes public)

@cero-miedo I'll leave it to you to close this if you think it's appropriate!

[pipetogrep]

We finally could complete our initial review of pgBackRest documentation in pgbackrest-docs. The old feature branch (docs_development) has then been merged into staging and main.
Would you by any chance have the possibility to adjust the "edb docs" system to automatically listen to the staging branch and refresh the staging environment on each commit ?

[epbarger]

I can totally adjust the code to pull from the staging branch. Until I get a bot user that can read from the private repo though, we'll still need to update manually, since github actions won't have permission to pull the code from the backrest repo otherwise