lxc-php-buster #85

Closed
Ghost wants to merge 7 commits from lxc-php-buster into unstable
First-time contributor

From now on we should use a buster container to run PHP 7.3 in a multi PHP environment. This will prevent PHP to be upgraded to version 7.4 and likely to break things.

I've already run this but I'd like the change merged into unstable so that others can test it.

From now on we should use a buster container to run PHP 7.3 in a multi PHP environment. This will prevent PHP to be upgraded to version 7.4 and likely to break things. I've already run this but I'd like the change merged into unstable so that others can test it.
Owner

Yes!

I see you went for opensmtpd as a replacement for ssmtp on buster. That's cool, but I've got few remarks :

  • Since it's a running daemon, we have to monitor it :/
  • It seems that you'll directly send mail. I'd relay it through the postix daemon on the host (ie: so you have only one place to setup opendkim)
  • I'd aim for the same solutions on all containers on the same host. While I'm "okay(ish)" with old servers still having ssmtp. I really think that new ones should have the same thing for email in each container.

Also, have you tried any other solutions like msmtp ?

Yes! I see you went for opensmtpd as a replacement for ssmtp on buster. That's cool, but I've got few remarks : - Since it's a running daemon, we have to monitor it :/ - It seems that you'll directly send mail. I'd relay it through the postix daemon on the host (ie: so you have only *one* place to setup opendkim) - I'd aim for the same solutions on all containers on the same host. While I'm "okay(ish)" with old servers still having ssmtp. I really think that new ones should have the same thing for email in **each** container. Also, have you tried any other solutions like msmtp ?
Author
First-time contributor

My answers in order :

  • It's a good point and I haven't thought about it. Maybe we could amend the SMTP check in order to make sure all the daemons are running (the one on the host and the ones in the containers)
  • Silly me, of course, it makes sense! That should be fixed by d625d840a9
  • I agree with you, we should decide to use the same solution for all containers

I didn't look into msmtp…

My answers in order : * It's a good point and I haven't thought about it. Maybe we could amend the SMTP check in order to make sure all the daemons are running (the one on the host and the ones in the containers) * Silly me, of course, it makes sense! That should be fixed by d625d840a9 * I agree with you, we should decide to use the same solution for all containers I didn't look into msmtp…
Owner

Nice work guys. Could we organize some tests of msmtp ?

Nice work guys. Could we organize some tests of **msmtp** ?
Owner

obsolete

obsolete
jlecour closed this pull request 2022-06-06 18:29:58 +02:00

Pull request closed

Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: evolix/ansible-roles#85
No description provided.