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

remove ng stuff #255

Merged
merged 6 commits into from
Apr 20, 2019
Merged

Conversation

k-hamza
Copy link

@k-hamza k-hamza commented Feb 26, 2019

Changes

  • remove "-ng" stuff
  • correction in listen directive when vhost is disabled
  • Tested on rhel7

@alxwr alxwr self-assigned this Mar 2, 2019
@alxwr alxwr requested review from aboe76 and javierbertoli March 19, 2019 08:39
Copy link
Member

@alxwr alxwr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k-hamza I really like what you did here. :-)
(The change request is only for that one hardcoded path.)

I'll test the dev branch in a small setup I'm going to build in a few days.


This state can create symlinks based on basic Core Rules package. (Debian only)
Or it can distribute a mod_security rule file and place it /etc/modsecurity/
All necessary data must be provided in the pillar
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aboe76 @javierbertoli I'd merge this PR as-is, but do we want to add another PR which implements the TOFS pattern?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alxwr Let's finalise the portable TOFS implementation in saltstack-formulas/systemd-formula#27. This should lead to a drop-in solution using libtofs.jinja.

apache/config.sls Outdated Show resolved Hide resolved
Copy link
Member

@aboe76 aboe76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k-hamza nice work, are there any deprecations?

@k-hamza
Copy link
Author

k-hamza commented Mar 22, 2019

@aboe76 still some work to do, but at the end it shoudn't have deprecations (if i didn't miss something)

for now it supports only rhel7/httpd 2.4

to support other systems :

  • rhel / httpd 2.2 : must add file apache/defaults/Redhat/defaults-apache-2.2.yaml
  • Debian :
    • add file apache/defaults/Debian/defaults-apache-2.2.yaml
    • add file apache/defaults/Debian/defaults-apache-2.4.yaml
    • adapt apache/conf.sls to manage specific conf files to this Os
  • Suse :
    • add file apache/defaults/Suse/defaults-apache-2.2.yaml
    • add file apache/defaults/Suse/defaults-apache-2.4.yaml
    • adapt apache/conf.sls to manage specific conf files to this Os

... same for other systems

i think there is a discussion to have about config.sls :
may be split it this way :
config.sls contains common code and at the end include config-{{ grains['os_family'] }} that will manage specific system conf files :
config-RedHat.sls
config-Debian.sls
config-Suse.sls
...

And about init.sls :
put the content of init.sls in a new file pkg.sls or install.sls
init.sls may contains only some includes

should these adaptations be added in this PR or in another after the merge of this one ?
i am not familiar with other systems, so it may take me some time to achieve that. if you can help i wouldn't say no :-)

@aboe76
Copy link
Member

aboe76 commented Apr 20, 2019

@k-hamza I have thought about it, sorry it took some time:

Would love to see suppport for other OSes in a different PR,

Splitting the config.sls, you could create a folder config
in which you can have init.sls (for common stuff) and include
RedHat.sls, Suse.sls, Debian.sls for each OS.

Leave the main init.sls as is for now maybe in a later PR this can be refactored.

By the way, I'm merging the current PR in the develop branch.

@aboe76 aboe76 merged commit ba23689 into saltstack-formulas:develop-v1.0.0 Apr 20, 2019
@k-hamza
Copy link
Author

k-hamza commented Apr 23, 2019

ok for config folder, (need some time to learn about the specificities of other systems)
And thanks for the merge !

@k-hamza k-hamza deleted the develop-v1.0.0 branch April 23, 2019 10:30
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

Successfully merging this pull request may close these issues.

4 participants