https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35716
--- Comment #9 from David Cook <[email protected]> --- Of course, I think this actually represents an opportunity to take it further! "tmpl" stands for templates, and templates are processed server-side. They shouldn't be web-facing! So let's think of a new structure! E.g. Git: "/kohadevbox/koha/public/shared/static" Package install: /usr/share/koha/public/shared/static Apache: Alias /shared /usr/share/koha/public/shared -- Eventually, we'd have "/public/opac" and "/public/admin" as well. (One of the advantages of using the "public" directory name is that it reminds you that whatever is located there will be served publicly.) These would contain "static" and "cgi-bin" directories for our static assets and CGI scripts. And the "templates" would move to /usr/share/koha/templates (or /tt or /tmpl or whatever), so they're not web/internet-facing. They're just available server-side as they should be. One day, "C4" and "Koha" will move into the "lib" folder in the git source tree as well. This is a code organisation which is super common elsewhere and I use it on lots of other apps. In the long-run, it would make it much easier to develop/maintain and securely run Koha. Eventually, the contents of /kohadevbox/koha and /usr/share/koha will be more closely aligned. (Obviously, only the /kohadevbox/koha will have things like "t", "xt", etc.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
