-
Notifications
You must be signed in to change notification settings - Fork 731
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
Don't drop zammad.conf into /etc/nginx/sites-enabled/ #1196
Comments
Whats your point? Eidt: Now i see what you've done. You renamed our config file so Zammad installed a new one, when updating. Can't work . Don't rename our config file. |
It is usually best practice to install new configuration files into Especially since the configuration file (per default) only contains HTTP you (as an admin) will probably end up writing your own or adjusting them anyway being able to disable the vendor configuration & using it as reference (for the proxy setup etc) is probably a sane idea. My recommendation would be to only drop a configuration file in |
I sincerely hope you'll reconsider this. Installing example contrib configuration into a production setup should not be done. |
Fully agree to @andir |
The configuration script is run after the package installation so there is no save way to check if it's the first installation or not and therefore it makes no difference if you use a symlink or not. |
Well in the simplest scenario you would this a `test -f` in there to detect
an upgrade. Packages are clearly able to perform different behaviours
depending on (first) install and upgrade. Think about databases migrating
you existing files etc...
…On Jun 23, 2017 6:39 PM, "André Bauer" ***@***.***> wrote:
The configuration script is run after the package installation so there is
no save way to check if it's the first installation or not and therefore it
makes no difference if you use a symlink or not.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1196 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAm_dK9PdJdzrZCyfvuYpmJknzdZ778Rks5sG-oigaJpZM4OBDiJ>
.
|
If you already have an idea: https://github.com/zammad/zammad/tree/develop/contrib/packager.io Pullrequest welcome. |
Ok, I had testing for the symlink in mind, what would of course not work, but checking for the file itself in sites-available could be a solution, at least for Debian family systems. As far as I remember centos & suse had no available / enabled dirs... I'll do it for Debian as soon as I have some spare time. |
Its fixed now in: 52baed5 |
Thank you! 👍 |
Infos:
Expected behavior:
Actual behavior:
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: