Skip to content
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.

Update to redesigned Content Security Policy support of debops.nginx #152

Merged
merged 2 commits into from
Apr 19, 2017

Conversation

ypid
Copy link
Contributor

@ypid ypid commented Apr 12, 2017

@carlalexander Can you merge this on 2017-04-15 so that it works seamlessly with the redesigned interface? Your feedback is very much welcome on the matter even after the Apache changes have already been merged.

Depends on: debops/ansible-nginx#156

@ypid
Copy link
Contributor Author

ypid commented Apr 15, 2017

@carlalexander debops.nginx v0.2.0 has been released. Can you check this PR?

@carlalexander
Copy link
Owner

I'll try to check this tomorrow. Sorry busy today 😞

@carlalexander
Copy link
Owner

My first run at testing this PR didn't work. The site was unavailable to connect. debops.nginx seems to be working alright, but there might be stuff missing. Do we have to configure debops.ferm ourselves now?

I also ran into this issue with debops.postfix. Might need to find a way to remove it as well.

@ypid ypid force-pushed the update-to-debops.nginx-0.2.0 branch from b591272 to 34a8971 Compare April 17, 2017 07:40
@ypid
Copy link
Contributor Author

ypid commented Apr 17, 2017

Do we have to configure debops.ferm ourselves now?

Yes, I removed them finally in compliance with debops/debops-playbooks#192. I did not check the used playbooks initially. I have currently no deployment of wordress. Updated.

@carlalexander
Copy link
Owner

This seems to be working alright. I'm running into issue with debops.php and debops.fail2ban, but it's not related to these changes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants