add official nginx repository to get newest version on ubuntu
like in https://github.com/geerlingguy/ansible-role-nginx/issues/237 mentioned, I added the official Nginx repository to get the newest Nginx version on older Ubuntu versions
I think this will not get accepted unless you add it for all supported distros. https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/#installing-prebuilt-ubuntu-packages
We might just allow for this ppa to be added, seems to me more up to date: https://launchpad.net/~ondrej/+archive/ubuntu/nginx
I think this will not get accepted unless you add it for all supported distros. https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/#installing-prebuilt-ubuntu-packages
We might just allow for this ppa to be added, seems to me more up to date: https://launchpad.net/~ondrej/+archive/ubuntu/nginx
@johnymachine Looks like the problem just exists for ubuntu. But feel free to add the other distros, I dont use anything else then ubuntu and cant test. To add the other ppa rejected geerlingguy already in another pr.
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This pr has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
I've been using this role for years now, it has saved me so much time.
Unfortunately for me, corporate is migrating away from RHEL to Ubuntu, and I'm faced with the problem that the default Ubuntu packages install an old and vulnerable nginx, and using PPA is also out of date (I get FAILED! => {"changed": false, "msg": "Failed to update apt cache: E:The repository 'http://ppa.launchpad.net/nginx/stable/ubuntu jammy Release' does not have a Release file."} on Ubuntu 22.04)
It's frustrating seeing a number of issues and PRs surface to solve this problem and all of them getting closed for sitting stale for too long.
- #202
- @geerlingguy mentions the issue in 2020, the issue goes stale and auto-closes in 2021.
- #207
- @shakalandy opens PR in late 2020, goes stale in code review, and auto-closes in late 2021.
- #223
- @lockejan picks up 207 and opens a fresh PR, PR is approved, but never merged, goes stale and auto-closes in late 2022
- #244
- @tbpoetke rehashes 223 and opens a fresh PR, goes stale in code review, and auto-closes in early 2024.
Is there something holding back these PRs from getting merged and a new version of this galaxy role rubber-stamped? I join with others in requesting someone smarter than me resurrect these PRs and see them through merger. Please? :)
As it stands, I am going to have to go ahead and incorporate (probably) 244 into my local clone so I can finish what I've started.