Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest nginx-ee/nginx-common/nginx-custom ok with this script? #13

Closed
chaddupuis opened this issue May 29, 2018 · 3 comments
Closed

Latest nginx-ee/nginx-common/nginx-custom ok with this script? #13

chaddupuis opened this issue May 29, 2018 · 3 comments

Comments

@chaddupuis
Copy link

First, thanks for this great script. I have just a quick question about the latest easy engine downloads and your script to ensure they are all ok.

I noticed on my server today the following packages have apt updates:
nginx-common nginx-custom nginx-ee

These are the underlying packages from easy engine as best I can tell (updated very recently) that your script updates. Should these updates be installed? or should the easy engine packages be removed from apt when using your script? or some other option? Eventually I will need to do a apt dist-upgrade for something and don't want to mess up our productive servers if these updates break the changes your script has made.

Please advise on the best course of action. Thanks!

@VirtuBox
Copy link
Owner

Hello @yyhmsg,

It's only a matter of choice, because the new nginx-ee release is up-to-date with Nginx v1.14.0, and the only differences with nginx-ee compiled with my bash script are the additional modules.
So, if you prefer to use the nginx-ee package available from the EasyEngine repository, you can install it to replace the compiled nginx.

You may have to make some changes in your nginx.conf because if you have used my nginx.conf example, there are some directives for additional modules not shipped with nginx-ee (rtCamp).

And you will have to use the following command to allow nginx package update (blocked by default in my script) :

sudo apt-mark unhold nginx-ee nginx-common

If you prefer to keep the compiled nginx, you still can update your packages with apt upgrade because nginx-ee and nginx-common are already marked as hold, and should not be replaced by nginx package from the apt repository.

@chaddupuis
Copy link
Author

I'd rather keep your script as it is more likely to be kept up to date. I see:

apt-mark showhold
nginx-common
nginx-ee

Should nginx-custom also be held back? or will that not matter?

@VirtuBox
Copy link
Owner

VirtuBox commented May 30, 2018

It doesn't matter, I have runned apt update && apt full-upgrade -y on my servers running with EasyEngine and the compiled nginx isn't replaced by the new nginx-ee release from the apt repository.

@VirtuBox VirtuBox closed this as completed Jun 2, 2018
@edisoncosta edisoncosta mentioned this issue Mar 20, 2019
2 tasks
@Rar9 Rar9 mentioned this issue Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants