https://bugzilla.redhat.com/show_bug.cgi?id=1420275 --- Comment #2 from James Hogarth <james.hogarth@xxxxxxxxx> --- This is just to sort of talk I'm hoping to engage with given the early developments of the container review process. In case you are not aware I am the owncloud maintainer in fedora/epel so am intimately aware of what it involves. This container is explicitly httpd+mod_php+mod_ssl as a minimal base, which is the predominant deployment I've found. This explicitly does not include a database (other than a test sqlite instance) but directs the admin to have a database served out of another host/container and that's an exercise for them. This is just one component - though the one most people expect - and is similar to the way it's packaged as a container upstream (not identical as it tries to take advantage of Fedora features and infrastructure). Rather than: > Official Fedora containers need to be examples of good containerized application design. and > This container should be sent back and broken into several services. I'd appreciate some constructive feedback (which is the point of reviews after all) on where you think a better split or an improved Dockerfile would worked out - particularly given the lack of guidelines at present. I care about these packages for some bizarre reason and I care about those who consume my packages. It was a crying shame when I had to retire owncloud from EPEL6 and point users elsewhere, when the time soon comes to retire from EPEL7 I'd really like to be able to point them to our containers to migrate to. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx