For better orientation, internally we have "red color" design for copr frontend (so users immediately know where they are).
It would be really useful if paths to template files were configurable via FE configuration file .. so non-Fedora instances could simply "just" edit config, instead of downstream-patch many template files.
Ideally, even the alternative design(s) should be "upstreamable" .. so we could e.g. submit patch adding alternative design. But admin's should be able to provide alternative 'copr-frontend-design-XXX' packages.
WDYT? Would be patches implementing this idea accepted?
Pavel
On Wed, Sep 21, 2016 at 5:56 PM, Pavel Raiskup praiskup@redhat.com wrote:
For better orientation, internally we have "red color" design for copr frontend (so users immediately know where they are).
It would be really useful if paths to template files were configurable via FE configuration file .. so non-Fedora instances could simply "just" edit config, instead of downstream-patch many template files.
Ideally, even the alternative design(s) should be "upstreamable" .. so we could e.g. submit patch adding alternative design. But admin's should be able to provide alternative 'copr-frontend-design-XXX' packages.
WDYT? Would be patches implementing this idea accepted?
I definitely like this idea. It's also implemented in Koji (and we use this feature in Fedora, Russian Fedora)
Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
The idea of configurable template paths sounds nice. What you can do now is to pass template_folder="xyz" as named param to flask.Flask constructor in coprs_frontend/coprs/__init__.py. In theory, we could keep that param value in db, so that no patching is needed.
clime
On Wed, Sep 21, 2016 at 5:56 PM, Pavel Raiskup praiskup@redhat.com wrote:
For better orientation, internally we have "red color" design for copr frontend (so users immediately know where they are).
It would be really useful if paths to template files were configurable via FE configuration file .. so non-Fedora instances could simply "just" edit config, instead of downstream-patch many template files.
Ideally, even the alternative design(s) should be "upstreamable" .. so we could e.g. submit patch adding alternative design. But admin's should be able to provide alternative 'copr-frontend-design-XXX' packages.
WDYT? Would be patches implementing this idea accepted?
Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel@lists.fedorahosted.org
-
Igor Gnatenko -
Michal Novotny -
Miroslav Suchý -
Pavel Raiskup