Add augur running in prod document

[AumOzaa]

Description

• Added documentation for AUGUR_RESET_LOGS environment variable to the production setup guide. This PR fixes #

Notes for Reviewers

• Added documentation only.
• Please let me know if this should be added to a different file or section

Signed commits

• [ ] Yes, I signed my commits.

[MoralCode]

@AumOzaa it looks like you just included/rebased a LOT of changes from main into this PR.

Can you update your fork to match the latest version of the main branch and base your commits on that? Happy to help guide you through this process if you would like

[AumOzaa]

I fetched the latest upstream changes and rebased my branch (add-augur-reset-logs-docs) on top of the updated main branch.

The rebase went through successfully and I pushed the changes, but now some error from the run-linting-checks workflow, specifically the check docs step is coming up.

I haven’t modified anything outside the documentation file, so I’m not sure why that’s happening. Could you please guide me on what might be causing it?

[MoralCode]

I fetched the latest upstream changes and rebased my branch (add-augur-reset-logs-docs) on top of the updated main branch.

looks like your rebase includes an extra commit not related to this PR: a4d9efcc713faf647d41053ee7c944f7d1899136

[AumOzaa]

I’ve removed the unrelated commit a4d9efc from the branch and also updated the toc.rst file to include the new documentation. I verified the changes locally by running make clean && make html, and the build completed successfully.

Looking forward to any feedback or further updates if needed.

[MoralCode]

looks good! Seems like the DCO check is still detecting that a couple of the commits are not signed off.

you should be able to resolve this with another quick rebase git rebase HEAD~5 --signoff

[AumOzaa]

I’ve done the rebase with --signoff as suggested, all recent commits should now be properly signed off. Please let me know if there’s anything else I should adjust.

[MoralCode]

I think this is ready - holding off on marking as such until the current release has been made

[AumOzaa]

Thanks a lot for your help throughout the PR process. Learned quite a bit about managing rebases and keeping PRs clean. Really appreciate your guidance and patience

[AumOzaa]

Sure, I’ll check the older PR and integrate it into my doc so it’s more general.

[AumOzaa]

I noticed the Podman e2e test failed, it’s possible I accidentally fetched some unrelated commits again? Could you please advise if that might be the cause, and if there’s anything I should do to fix it? Also, I’ve combined the content with the previous PR as suggested, does the documentation now look general enough, or are there any further changes needed?

[MoralCode]

I noticed the Podman e2e test failed, it’s possible I accidentally fetched some unrelated commits again? Could you please advise if that might be the cause, and if there’s anything I should do to fix it? Also, I’ve combined the content with the previous PR as suggested, does the documentation now look general enough, or are there any further changes needed?

Dont worry about that test, its been acting up a little lately. you only made changes to the docs so as long as the docs build works you are fine

[MoralCode]

If you can, you should also go back and signoff your commits too!

[sgoggins]

@AumOzaa / @MoralCode : I am rerunning hte end to end tests that failed to see if they just timed out or if there is a problem.