6 ms·

Slightly OT: Does anyone know if packages for Ubuntu 14.04 are coming soon? We're using the official (mainline) repository[1] on Ubuntu 12.04, but Trusty doesn'

by pfg 13y ago

Slightly OT: Does anyone know if packages for Ubuntu 14.04 are coming soon? We're using the official (mainline) repository[1] on Ubuntu 12.04, but Trusty doesn't seem to be supported yet. I've always preferred the official repository because I didn't want to start compiling nginx just for stuff like SPDY support. [1]: http://nginx.org/en/linux_packages.html http://nginx.org/en/linux_packages.html

jolan 13y ago
Looks like they exist, just not mentioned on that page yet. http://nginx.org/packages/ubuntu/dists/trusty/nginx/binary-amd64/ http://nginx.org/packages/ubuntu/dists/trusty/nginx/binary-a...
jallmann 13y ago
It's a good idea to be comfortable compiling/packaging your infra from source (including interpreters, libraries, etc), if only for the ability to quickly apply and deploy emergency patches. To demonstrate the importance of that capability, look no farther than Heartbleed. While distros are usually pretty good about updating critical software, they shouldn't be your only line of defense, except perhaps if you have a SLA or something.
- pfg 13y ago
  I agree, although I'd stick with packages for almost anything as it's just too much work to keep up with every release of every piece of software in your stack (except for, as you mentioned, special circumstances like Geartbleed). Plus, since in this case the repository is managed by nginx.org, it's hard to beat them to a new release even if you compile from source.
- nlindblad_se 13y ago
  https://niklaslindblad.se/2014/03/build-statically-compiled-nginx-147-with-spdy/ https://niklaslindblad.se/2014/03/build-statically-compiled-...
- rhoml 13y ago
  Agree on this, and also most of the production apps don't require the same modules.
- lamby 13y ago
  > It's a good idea to be comfortable compiling/packaging your infra from source Would highly recommend becoming comfortable making your own packages (with any security updates, misc changes, etc.) over compiling and installing your own stack from source - distro packaging really is mostly your friend.
  - MichaelGG 13y ago
    nginx still has a critical bug with SPDY and proxy_cache which causes connections to be aborted on cache hit. SPDY with proxypass+cache is fairly unusable without this patch. http://trac.nginx.org/nginx/ticket/428 http://trac.nginx.org/nginx/ticket/428
jafaku 13y ago
I don't know, these things are always outdated so I always install from source.
- pfg 13y ago
  In my experience the official packages are always up-to-date, as soon as I receive the release announcement, apt-get update will have the latest version ready.
  - thresh 13y ago
    The packages are usually uploaded within a couple of hours after the release announcement. It took it a big longer this time because there were two releases. :)
thresh 13y ago
The packages have been uploaded as far as I can see.

by pfg 13y ago

jolan 13y ago

Looks like they exist, just not mentioned on that page yet. http://nginx.org/packages/ubuntu/dists/trusty/nginx/binary-amd64/ http://nginx.org/packages/ubuntu/dists/trusty/nginx/binary-a...

jallmann 13y ago

It's a good idea to be comfortable compiling/packaging your infra from source (including interpreters, libraries, etc), if only for the ability to quickly apply and deploy emergency patches. To demonstrate the importance of that capability, look no farther than Heartbleed. While distros are usually pretty good about updating critical software, they shouldn't be your only line of defense, except perhaps if you have a SLA or something.

pfg 13y ago
I agree, although I'd stick with packages for almost anything as it's just too much work to keep up with every release of every piece of software in your stack (except for, as you mentioned, special circumstances like Geartbleed). Plus, since in this case the repository is managed by nginx.org, it's hard to beat them to a new release even if you compile from source.
nlindblad_se 13y ago
https://niklaslindblad.se/2014/03/build-statically-compiled-nginx-147-with-spdy/ https://niklaslindblad.se/2014/03/build-statically-compiled-...
rhoml 13y ago
Agree on this, and also most of the production apps don't require the same modules.
lamby 13y ago
> It's a good idea to be comfortable compiling/packaging your infra from source Would highly recommend becoming comfortable making your own packages (with any security updates, misc changes, etc.) over compiling and installing your own stack from source - distro packaging really is mostly your friend.
- MichaelGG 13y ago
  nginx still has a critical bug with SPDY and proxy_cache which causes connections to be aborted on cache hit. SPDY with proxypass+cache is fairly unusable without this patch. http://trac.nginx.org/nginx/ticket/428 http://trac.nginx.org/nginx/ticket/428

jafaku 13y ago

I don't know, these things are always outdated so I always install from source.

pfg 13y ago
In my experience the official packages are always up-to-date, as soon as I receive the release announcement, apt-get update will have the latest version ready.
- thresh 13y ago
  The packages are usually uploaded within a couple of hours after the release announcement. It took it a big longer this time because there were two releases. :)

thresh 13y ago

The packages have been uploaded as far as I can see.