| Summary: | Suggestion: pseudo-webapp that sets up skeleton dirs via webapp-config | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mike Nerone <mike> |
| Component: | New packages | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | 2004.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
wrobel: should we add this to w-c? No, this ebuild would just create three directories. The structure is created once you install any of our webapps. I don't really see a benefit in having this. Marking as won't fix for now. |
Just a thought: Purely as a convenience for Gentoo users, since webapps (i.e. ebuilds that inherit the webapp eclass) create a good skeleton directory structure for a site (cgi-bin, htdocs, icons, etc. with proper permissions), perhaps it makes sense to have a pseudo-webapp ebuild (say, "webapp-skel") that does ONLY that. Once that's merged, an empty site can quickly be setup with webapp-config -I -h www.example.com webapp-skel <ver> Such an ebuild is, of course, trivial: ======================================================================== IUSE="" inherit webapp DESCRIPTION="webapp-skel is a pseudo-webapp that simply sets up skeleton dirs for a web site." LICENSE="GPL-2" KEYWORDS="x86" src_install() { webapp_src_preinst webapp_src_install } ======================================================================== On the other hand, this may be something that's slated for vhost-config (unless that *is* webapp-config - there's still uncertainty on this out here in the non-dev world).