documentation
documentation copied to clipboard
rocky-linux
documentation/docs/guides/security/generating_ssl_keys_lets_encrypt.md -- Nginx Not available RL9
The guide stays to install dnf install certbot python3-certbot-nginx does not work, however it appears that dnf install certbot python3-certbot-apache still is available.
The nginx package is missing.
Hello @xgpt and thank you for your comment. This procedure has not yet been tested for RL9 and it is certainly possible that the package is not available. If so, it would be unavailable from the upstream packages as well. I'll do a little research for you and see what I can find out.
The guide stays to install dnf install certbot python3-certbot-nginx does not work, however it appears that dnf install certbot python3-certbot-apache still is available.
The nginx package is missing.
I was able to find this issue. The reason that you are not finding this package:
1.) these packages are (were) provided by the EPEL in Rocky 8.x and the same holds true for 9. In other words, when they are available, they will be coming from the EPEL. 2.) As of right now, there is a version in testing on EPEL 9, but none in stable. You can see this here: https://src.fedoraproject.org/rpms/python-certbot-nginx (Section Fedora EPEL9)
When this moves out of testing into stable, the package will be available (again, not from Rocky Linux, but from the EPEL). Hope this helps!
This does help! I had assumed as such, but I'm concerned about the quality of documentation and would like to assist some. Frankly I'd like to see a "last tested with RL8 on January 1st 2021" or some such tag on these documentation sheets. Would it be possible to mandate tagging last tested dates for documentation commits going forward? If it would not be impossible I believe it would be extremely useful to see when documentation was written, so that we don't end up going halfway through a guide and then scratch our heads wondering why something doesn't work. It's not newbie friendly to have documentation that is not dated and tied to a distro version, unless it is and I'm just a dunce and not seeing it.
Okay, I see that it's there as March, but don't see RL8/RL9/etc. Would be nice to know how to get in touch with a documentation leader to relay the idea of tagging guides/documentation with the release last tested. Any ideas how I could do that?
The meta tags do include, particularly if the document has been edited or modified recently, a "tested with:" meta. This meta includes the versions of Rocky Linux that a procedure has been tested with. A request has been made to the web team to add these tags visibly to the bottom (where the "author" and "contributors" meta already shows), but as yet there has been no activity on this front. I'll try to bump this with the web team to see if perhaps we can push that forward.
@xgpt Thanks for your interest in contributing! We can definitely use your help.
@xgpt Since the EPEL now includes this package, the procedure should work for all current Rocky Linux releases. I'll close this issue for now, but if you still have issues, please feel free to open a new issue on this.